I disagree. There are plenty of programs that run just fine on Wayland.
I acknowledge the effort that OP has put into this project. And if the OP plans to use X11 for the foreseeable future, then it makes sense to target X11. But for any new project with a wide audience Wayland is a much more reasonable target.
There is no way to "target wayland" for a tool like this. For security reasons pretty much everything this tool does is blocked on wayland. You could perhaps make a version for sway and other wlroots-using desktops that works mostly like the current tool. For GNOME you might be able to get away with rewriting it in JS as a shell extension, no idea for KDE.
IMO, a position of "LOL, it works just fine on Wayland, just write it from scratch in six different programming languages to cover 80-90% of DEs/WMs out there" is not very developer (or for that matter, user) friendly. At least X11 is a single interface to target.
What's interesting is, very often, "for security reasons" is a complete BS kludge to say "we don't want to implement this." I normally wouldn't expect that sort of thing from Linux folk...perhaps until now.
I literally just recently had to switch a brand-new Ubuntu installation to X11 because Synergy/Barrier wasn't working in Wayland mode [0]. Until Wayland gets its head in the game, I'm staying on X11 for as long as possible.
