It has a compositor, which could be considered more equivalent to X11 window manager than to X11 server. The compositor handles display and input by itself (using KMS, DRI, libinput, etc.). Examples are Gnomes Mutter, KDEs KWin and Sway.
Among other things it means less context switches and synchronization when trying to display something, smoothly.
remote windowing support.
that would be great for the ecosystem.
If the point of Wayland is to replace "unmaintainable mess" that X supposedly is, they should show how to provide better protocol for X features, instead of cutting them off and claiming they solved something.
Extremely vocal minority users like you and the others on Hacker News are simply not in anyone's support matrix. Luckily, all of you folks crying for the lack of this feature are all tech experts - if you want it, go code it up yourself.
Meanwhile, anyone and everyone else that cares will just switch to VNC and move on as if nothing happened.
So basically, nobody noticed, because nobody is using it in this scenario. That occasional remote dbca session doesn't count ;)
One perfectly legitimate way of doing that is to do one of those things and ask others to do the other things. Development would not go faster, if they put those other aspects at the end of their To-Do List as well.