It's a bit deeper than just a series of bugs. For all of Linux's power and freedom, its modern desktop architecture is extremely restrictive.
* There is only one systemd --user session per user with one D-Bus instance. So you can only have one desktop instance active at a time.
* There is no way for privileged apps/scripts to generically control the desktop or other apps in Wayland. (so no accessibility, AI computer use or even general scripting)
* There is no differentiation between configuration that should be active on (user, machine) tuple, and configuration that should be active on (user, *) tuple. (even Windows gets this right!)
* Desktop apps do not report rich activity information so they cannot be smartly memory managed.
* Desktop apps cannot generally be restored after getting killed/system shutdown.
* No application identity, PIDs voluntarily take on application identities in Wayland and on D-Bus, but PIDs that don't can easily escape observability, and if they consume resources but not enough to show up high in top, good luck knowing about them.