You can Wayland advantages some of the most glaring improvements as the negative of the X11 known issues.
But what you don’t see is the engineering nightmare X11 had become, with protocols with different on wire formats, heavy IPC, synchronousity, old un-removal protocols…
There is a point where a code-base cannot evolve sustainably. X11 reached this stage years ago, and the then X11 developers made the wayland architecture.
Like the security trench ?
You never-ever had any tearing ?
By all means keep using X11, if that fits your needs.
Wayland is not perfect by any means and its design and limited scope induced some churn. The wayland compositors are already replacing X11 fine with a more dynamic community and cross-compositor collaboration and allowing experimentation.
One of the nice developments in recent years has been the introduction of new APIs for tasks such as screen capture/casting.
Previously programs like simplescreenrecorder had to each have their own, application specific, workaround to implement this missing functionliaty. Now they can just use the new standard API.
With the added bonus that it works regardless of whether they run in an X11 or Wayland session and regardless of whether they run as a system installed program or from within a Flatpak/Snap sandbox.