The creators of Wayland decided that it is not their task to handle remoting. You could argue that this demphasizes the issue, leaving it to insufficient VNC, dead projects like NX, or not yet production ready projects like X2Go (once they support Wayland that is).
That seems to be their decision but I can't imagine what's motivating them. How is the non-remote use case even relevant at this point? Is Wayland intended for console gaming?
What Wayland is not is a protocol designed for remote transport over TCP. Neither was X11, mind you. There are other, better, protocols like this, like RDP, VNC, and SPICE. These protocols use techniques from video compression and instead of shared memory.
You can use VNC and RDP with Wayland.
Also, VNC is nothing like the network transparency of X11. In X, I am able to run a single application on one machine, connecting to an X server running on a different machine. The application will be a first-class citizen in the user environment. This is in contrast to the VNC case where it lives in a separate desktop that is forwarded as a whole to be displayed in a window on the receiver side.