Glad to help. I've only been using Wayland for a short while myself, and just ran into a huge problem I'd like to save you from. It has to do with VMs. I had replaced all my Solus VMs, plus a few others, including Windows 10. Having changed to Wayland had no effect on the VirtualBox system manager, but the VirtualBox window manager (as built into the VMs) is not in the least compatible with Wayland.
When I finally got around to launching my Solus Budgie VM today, it locked up the system tight -- no mouse, no keyboard, and so on. I tried everything I could imagine might help, and nothing did. Eventually I had to reinstall my operating system, update it, configure it, etc. I just finished with all that.
I decided to avoid creating any VMs until I can figure out how to do it safely, of course. I haven't researched that yet, but will do so soon. I'm sure there's a how-to somewhere on the net.
I was wondering whether you'd tried running a VM yet under Wayland? You use Boxes, and I use VirtualBox, of course, but they both use a KVM hypervisr, so I'd assume that they probably share that problem. If they don't, then Boxes might be a way for me to re-create a few of my VMs until I find out how to make Wayland work with VirtualBox.
But if you still actively work with Boxes' VMs, do so cautiously. You might find yourself rebuilding a host machine. My laptop and all the VMs employed hibernation, which may have contributed to the problem. Every time I restarted the laptop, I could never get far enough to fix anything before the Budgie VM was launched and locked up the system.
Perhaps if hybernation were not enabled there'd be no problem -- or, at least, not such a big problem. I'm not going to attempt even that until I've done some research and discovered whether I can do it safely, and if so,how.
