Yeah, I'm not sure why the entire X protocol had to be thrown away. I suspect for a while the shiny new desktop stack will just be X on Wayland until someone writes a Wayland compositor that is also an X server just without the bits that can't work. One of the reasons for Wayland was fast compositor updates, but I still don't see why the compositor and window manager have to be one and the same, you could delegate management to a wm and present the full window. Heck, you could also replace Xlib and xcb with versions that know when they're running locally and skip the network protocol for most operations.

Sadly I don't have time to work on that, which really sounds like a full time job for a team of at least 3 developers, and from the looks of it, the people in charge don't share my vision for integrated coexistence of old and new.