Wayland aims to be a less bloated protocol, and while it does do some things better than X11, most of the bloat comes from the X.org implementation of the X11 protocol. While Wayland claims to be less bloated, much of Wayland's bloat is passed on to the compositor, which has to implement all of that. Writing a Wayland compositor from scratch takes a lot of effort, requires implementing a lot of different protocols, compositing, window management and more. A Wayland compositor is pretty much a full Wayland implementation, and more on top of that. For this reason libraries like wlroots exist which write a lot of the boilerplate for you.
Wayland also combines the window manager and compositor, meaning you cannot write a window manager without writing a compositor and vice versa. If a compositor manages windows well, but sucks at compositing then you're SOL. While Wayland objectively provides better security than X11, Wayland clients are also not allowed to place themselves in a specific position of the screen in the name of security. So when you try to use --x-position and --y-position arguments in spmenu and find that they don't do anything, you know who to thank for that.
My dwm fork speedwm is quite bloated, but more importantly it's really slow for some reason. The project is now archived, and you should probably use dwm instead.
+OpenSUSE is a GNU/Linux distribution who seems to think that people who do not want to see LGBT colors when starting LibreOffice are rotten flesh and 'Cutting out the rotten flesh is healthy and needs to be done.'