As for the API stuff: why does the display server need to deal with power management? That sounds like something the power management API should do. IMO, the display server should just display things, not manage power states or login states. Wayland draws the screensaver, but the session manager controls the actual session.
Still, there is an open MR to accept this API (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/111) that needs to be rebased and needs a bug resolved. The solution falls perfectly in line with the GNOME way of doing things as well (forwarding the Wayland API to DBus so the DBus interface can do its thing), the only problem is that nobody is interested enough to do the hard work.
DBus is an excellent method to communicate anything that doesn't involve exchanging buffers. Many members of the Wayland project are trying to prevent going down the same path X11 went down, sucking up more and more features and API surface and becoming a huge, unstable, buggy mess because of its sheer code size.
As for your mouse cursor issue, Wayland's cursor_theme seems to be supported by at least. I can't find cursor_theme in the Wayland spec itself (there is a merge request at https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i... but I don't see much activity) so until that gets stabilized you can choose between using DBus or a bespoke, DE-specific API, pick a compositor that takes away cursor control from the application entirely, or switch back to X11.