Lack of network transparency in Wayland in roughly matched by the lack of network transparency in 'ls'. Yet I can run "ls" on my NFS filesystem without trouble.
If you want network transparency, you get to use two protocol converters. One that runs on the same machine as your applications, appears to be a Wayland server, and flings images over the network in some way. The other runs on the same machine as you display, acts as a Wayland client, and hands the images over to be displayed. Similarly input events are passed back.
I can easily imaging 'ssh' growing functionality to start these two protocol converters for you (if so configured) - just as it currently will transparently set up X forwarding over the secure connection, with X-authentication handling. Then you should "ssh myhost may-gui-app" and it would "just work" just like it does now.
So lack of network transparency in Wayland isn't a problem - it is an aspect of the well-structured design.
And fear that developers of some project might drop some functionality that you find valuable certainly has some validity (see also Gnome-3) but tying that fear to the functionality of some other project seem hard to support - peoples reasons for breaking things are usually quite different to the reasons that you expect.