Wayland is far from mature, even with xorg-xwayland.
I personally use it with (fairly uptodate) KDE/Plasma on a Intel Iris Xe Graphics, and still get some annoyances.
1) I’ve been daily driving Wayland for six years and the only pain I have is that IntelliJ is blurry at 4K
2) Nothing in the parent comment even mentioned Wayland, unless it has been edited- they're saying that people don’t run X.org as root these days (which I am not certain of, since I haven't been running it for so long)
For example: Inter-application communication to allow time-tracking apps, automation, accessibility, and a thousand other use cases. (I can't live without barrier and x over ssh)
Wayland is designed to block this feature. Which means it will always remain a niche, only useful for those running multiple monitors with different refresh rates. And even those people are limited to AMD GPUs. So that's a very small niche of a very small niche.
And KDE just built a screen recorder for Wayland. But why bother rewriting all of these tools, when perfectly good, battle-tested solutions already exist in X? Many software makers are unwilling to rewrite their apps from the ground up just to work on a niche system.
Yes, they have made that quite clear. I think it is a real shame that so much time has to be given fixing bugs and recreating software that already exists, rather than developing interesting new software on a stable platform.
It is not designed to block this feature, it just has absolutely nothing to do with a goddamn display protocol. The linux userspace is definitely lacking in many other areas but that is simply due to no unified solution (inherent in bazaar style development), and an insane reliance on C for everything.