-- If you want to see responsiveness try gnome2 applications either locally or remotely and compare them to the current ones locally even with a video card accelerating things for you.
Sure. Try your experiment. Have several video streams going in different windows and rapidly move the windows relative to one another. Or try anything else that requires a high framerate and lots of video information.
-- Blaming network transparency is just a distraction from losers who wouldn't know how to get their stuff running well on any platform. It never had anything to do with responsiveness because local applications get to use local sockets.
Network transparency in the proper sense doesn't exist on modern interfaces. If you mean how they fake it then yes that has an impact on performance. We've talked about this before. You can't safely directly render to X11's compositor without a high risk tearing. The application can't tell the compositor how to render and so half rendered content gets displayed. That's not ignorance it is deep design. To solve this applications render to a buffer and then do a memory copy. The speed of the memory bus is going up, but much more slowly than resolutions so this problem has gotten worse not better since Wayland started.
High performing applications need to control the rendering process cheaply.