So your complaints have nothing to do with Wayland itself then.
Again all this hate is misdirected. The toolkit level comment is absurd. The compositor is responsible for remote desktop. The developer's comments were only that remote is neither mandated nor impeded at the protocol level and they wouldn't focus on putting it in the reference compositor Weston. I think people fundamentally forget that Wayland is a protocol.
But if you think the recent dramas are in any way special then you should look into the history of things. The past had it's share of dramas, typically with RedHat plowing forward and doing it's own thing. The only thing that is really new as of late is that Debian, a former example of how to make a feature stable and conservative OS is starting to move to systemd. The rest of the stuff doesn't surprise me much.
I think people in generally forget the reason why there are so many different Linux distributions, and people generally forget why there are so many different packages. Take Gnome for example. Gnome is now dependent on logind, which is dependent on systemd causing distributions to switch sysvinit to systemd. However that's not it at all. Gnome is dependent on an API for user management. Why not implement it separately? I saw talks of one project forking logind and decoupling it from systemd, and then everything goes back to normal and Gnome can run on any init system. THAT is how Linux used to be run.
These days it's all threats of forks and then bending over and taking whatever is on offer because it's my favorite distro or some such thing. 20 years ago for end users it was a case of well Debian didn't work... I'll try Slackware. Now we all have collective Stockholm syndrome.