I don’t think that such a comparison is relevant. And if you mean “dealing with KDE’s issues on Qubes OS will still probably take less of your time than alternatives” that would not necessarily be a sign of good software 
Especially when currently users would need to know to search or ask beforehand to get an idea of what they would be getting into, which is an issue in itself. The way I would look at it is that each unaddressed issue leads to some loss of potential users (not to mention time, etc.)
Anyway, while the serious issue with the keyboard layout seems to be actually not rooted in KDE packages, I think that the issue of the Wayland session being the default should also be taken seriously. It’s just a bad initial experience to be greeted with a non-functioning system, and it’s confusing, too. I bumped into it when I did an in-place upgrade from Qubes OS 4.1 to 4.2 (with many other issues along the way) and at first I didn’t notice, and I was surprised not that there was a new option in the drop-down menu, but that, at the same time, the new option would be the default one, even more so despite the fact that normally the last selection is remembered. After I had logged in I couldn’t tell exactly why (if I recall correctly) no qube window would open, while dom0 applications would open, and I had no obvious indication that this was Wayland and not X11.
So I’m sure that, if the situation is still the same, changing the default option (or alternatively, removing the Wayland option) would save in aggregate many user-hours of confusion, uninstalling, looking up, etc.