On the flip side, there's some software that works (somewhat) with wayland but deliberately breaks compatibility.

For instance, Scribus uses QT which supports wayland, but they hardcoded a check to explicitly detect wayland and exit if it's found. You get the generic QT "supported backends" message that lists wayland, but if you actually try to use it the logic resets your choice, gaslighting you into thinking you typed the backend detection or override env var isn't working.

You can get around it using a wayland-flavor that they forgot to reject, and there are bugs (not sure how many are from wayland itself and not Scribus though) so I get not wanting to handle wayland related bug reports, but having buggy software is often than having no software at all so I wish they didn't choose the nuclear option (and now they get "please support wayland" bug reports instead, so...).

I think Krita is the same? There were a couple programs I had to dig into the code to work around blocker mechanisms to get to run.

Scribus doesn't "deliberately" break compatibility; it was completely unusable with Wayland and they added friendly message. It also doesn't really go out of its way to do so as you're suggesting – it just checks Application::platformName() == "wayland" and that's it.

Maybe it's better now with Wayland and that check can be removed. I don't know.

See: https://bugs.scribus.net/view.php?id=16998 and https://github.com/scribusproject/scribus/commit/74d8d7ef7

Krita should work now.