The biggest hurdle for Wayland adoption is the absolutely brain dead "security model". Commonly used features like hotkey daemons, push to talk, screen recording/streaming/sharing, window management, clipboard history manager or even Wallpapers need to managed by the particular implementation (of there are many) of the Wayland server itself and have mostly no common protocols, at least not official. And when all those protocols after a long process are finally finished I have serious doubts that Wayland will be either less bloated and "messy" or more secure than current X11.
The non-existent X11 security model is not really ideal but at least you could mitigate the problem there with access control hooks and as long as you use trusted software (which is 99.9% the case on a typical Linux system) you can use all the above mentioned features today without having too much headaches.
The non-existent X11 security model is irrelevant considering on most systems anything under a uid can debug something else under a uid. Wayland's security is entirely pointless.
I suspect Wayland will just become a container for an X11 session.
The non-existent X11 security model is not really ideal but at least you could mitigate the problem there with access control hooks and as long as you use trusted software (which is 99.9% the case on a typical Linux system) you can use all the above mentioned features today without having too much headaches.