Wayland is not a thing you should be fighting

Who said I was fighting Wayland? I'm "fighting" against the misinformed "X is fundamentally broken" comments with something designed for slightly different tasks and still in early development held up as the instant replacement. It's not Wayland's fault that people take comments about using X on a phone out of context and hold those up as an example of why X should be instantly replaced with Wayland in all areas.

You know that what you had written was just an uninformed guess - somehow the GL backend is faster than GL for instance - and you attempted to gold plate your guesses with someone else's name despite it being your guess and not theirs. Why expect a polite response to such disgusting behaviour?

Do some background reading on the topic and watch it again.
An unfinished powerpoint with a few mistakes left in - such as an implication that X is slow just because gedit on gnome3 is slow (as distinct from it being much quicker to start on gnome2), is not convincing.

RDP/VNC does not do many to one like X does and are very inefficient screen scraping hacks - so not on topic at all you goalpost shifter.

So you are speaking for Raster now - piss off you name dropping liar until you come close to having a fucking clue about the topic instead of pretending that others that have actually done some work on it agree with you.

One like Wayland, which only provides surfaces applications can draw into

Or something like EVAS, which ironicly now also has Wayland support despite it being pretty well the canvas that Wayland is aiming for.

Also, you completely disregard the MUCH bigger number of administrators and helpdesk personnel working with VNC, RDP, Citrix etc.

NONE of those things is X windows.

What you missed above - "older versions of gtk".
The other thing you missed is "People using workstations in offices accessing stuff over X remotely" - WTF do you think they are accessing? It's not going to be Firefox they can run that locally. It's not going to be Thunderbird they are running that locally. It's not going to be Chromium they are running that locally.
Noticing a pattern yet? So think then - what on earth is so constrained that they cannot run it on their own box? You didn't think? I'll give you an example - in my workplace it's engineering and scientific software that only runs on RHEL5 (or CentOS) vintage linux, and either serious hardware requirements or licence requirements mean it makes far more sense to run on something big instead of locally. Such software has a long development cycle and a lot of it hasn't even got as far as considering gtk2 let alone gtk3. Surely you knew that or you would not know enough about the subject matter to be able to put together a useful reply - did I really have to spell all of that out just because you missed so many things in a very short post?
So I'll write it again in a different way - hardly anything being displayed remotely with X is going to be using those new toolkits so it's a rather stupid strawman to state that X is broken because some toolkits not in use much for remote displayed applications use a slow transport mechanism. IMHO it's also rather stupid to blame X for the choices made with those more recent toolkits - surely if anyone should be blamed it's whoever chose to change the behaviour in their toolkits? Blaming X for a gnome choice is like blaming a bridge builder for a Humvee breaking down half way across.

Conflict of interest is just what they do - ever wondered why there's a vast web of private contractors with points of failure (or patriotism) such as Snowden when it should really be a tight military operation? It's all about rewarding cronies. Retiring and getting millions funnelled into your pockets is far more lucrative than being promoted a rank.

Look halfway down the page - point II. The ignorant fucker who wrote that taking Daniel Stone's joke from the video linked above as a fact. Profanity is deserved since whoever wrote it failed to do a truly minimal amount of homework and is just wasting bytes and pixels.
Sorry, that is clearly just a derivative product of the video from someone that watched it without enough background to understand it.

Surely there's something other than that video from close to two years ago or a newbies review of it?

Only a couple of them, Daniel Stone and the xdamage guy. However there is a lot of X code in Wayland so some people have been retrospectively called "Wayland guys" to inflate the numbers. It's a bit of weasel trick from some fanboys so the actual Wayland developers shouldn't be blamed for such misguided cheerleading.

Surely you could at least have a link to the finished presentation instead of the error filled unfinished draft at linuxconf.au 2013 where he doesn't even have a screenshot and forgot his video cable?
The "X is slow because gedit takes a long time to start" (because it's loading half of fucking gnome3!) is one of the low points, another, which is not his fault just one of people misunderstanding, is where his joke about only three people understanding X input fell flat and had been cited by the clueless as a "fact"!
I got the impression from that video that it was an informal update on the state of Wayland and not meant to be taken as an authority on the subject, especially since his slides were not finished and he didn't have anything to back up some of his assertions mostly because he hadn't written that bit yet.
Also consider the context of it being about the suitability of X on telephones. Does it make more sense now?

Some gnome3 stuff is "most" now? People using workstations in offices accessing stuff over X remotely are still very unlikely to be running any gnome3 stuff from the remote machine. It's not "just motif", it's qt and older versions of gtk plus all the rest that do things sensibly instead of blitting bitmaps at frequent intervals.

They want to provide low latency at the cost of requiring high bandwidth, however X latency is not a problem if you have plenty of bandwidth so it's a non-solution to a strawman argument.

Daniel Stone has done a bit on X over the last 5+ years and the stuff he is interested in, the gnome3 stuff and phone software, is no longer network transparent. Everything else is, up to and including his Nokia implementation, but you've taken things out of context or heard a rumour that came from misunderstanding Daniel Stone's comments at linuxconf.au 2013.