Wouldn't that still suffer from all the problems that Wayland has?
It might solve some issues (permissions, screenshots, copy/paste) by fully enclosing a real X11 session in a single Wayland window, and allow it to use more modern video drives. The trouble is, I think it will make multi-monitor and laptop support considerably worse. Wayland composers (all of them) have a tendency to crash when you all/remove monitors. KDE has gotten better about this, but it's still not great.
Furthermore, it's impossible to see all your disconnected video adapters in any Wayland composer I've looked at. xrandr shows you all your disconnected ports (e.g. DisplayPort-1, HDMI-A-0, etc.) You can clearly see their connection status. There is
nothing like this in Wayland. In fact, there's no xrander. wlrander has to specifically support each composer/composition library (a lot of them use wlroots which makes it easier). Generic scripts for dealing with multiple monitors now have to be highly customized for each composer.
Wayland also sucks at KVM switches. No Wayland composer I've seen can handle a monitor disconnect if it's the last monitor. So it just crashes. If you have two monitors, Hyprland will move every workspace from the disconnected monitor. There is no way to disable this. i3/X11 has never had this problem.
Void Linux doesn't have a stable and unstable tree. Everything is a single "stable" rolling release. It makes python updates insane and it makes maintained 3rd party repositories for Void very difficult if not impossible. They also had some insane politics and wouldn't even consider adding Hyprland. The
3rd party Hyprland repository has constantly breakage issues due to the insane way xbps defines shared libraries dependencies in the shlibs file.
I liked Void for being a systemd-less distro. I still like void less and less these days, not just due to their political splurging over Hyprland and now Xlibre. More with how shitty the distro itself is put together.