Creating a wayland compositor based in wlroots is much more work than an X11 window manager. And then there’s quite a bit of work to keep up with new Wayland protocols.
But I personally don’t think there’s a need for more compositors, since the existing compositors do support all kinds of tiling.
E.g. river has custom layout providers, which allows for creating completely custom tiling behaviour. There’s even a hyprland plugin which implements river-layout-v3.
They are evaluating different ways to continue to support ad blocking. E.g. “unbraving” Brave Browser, or just implementing their adblock-rust.
They most likely won’t support MV2, since it would get increasingly difficult with each update to Chromium.
https://github.com/ungoogled-software/ungoogled-chromium/issues/662