This topic came up earlier and as explained in the linked thread its not yet reasonable stable to be the default for everyone. I’m using the Wayland session myself currently and overall love how smooth it feels, definitely! There are however a few things which happen from time to time and these are crashes!
λ coredumpctl | rg kwin
Sat 2021-05-22 21:16:40 CEST 1149 1000 1001 SIGSEGV present /usr/bin/kwin_wayland 12.2M
Sat 2021-05-22 21:56:52 CEST 511485 1000 1001 SIGSEGV present /usr/bin/kwin_wayland 9.2M
Sun 2021-05-23 19:24:54 CEST 2469 1000 1001 SIGSEGV present /usr/bin/kwin_wayland 12.3M
As you can see 3 crashes happened in the last 2 days alone - crashing kwin_wayland means the complete desktop restarts and programs will lose progress. As pointed out by @SameExpert, some people like us are actually not put off by that but the majority will lash out and blame Garuda for being buggy and they would be right doing so.
Another topic is compatibility of applications used. Lets take Kdenlive as example, this one currently just crashes if launched using Wayland. This requires workarounds which might not be feasible for end users.
Yet another topic is missing functionality of well known applications such as all screenshotting tools, screen capturing or VNC sessions (I’m not sure they dont work yet but I think I read something like this). Actually, KwinFT is working on providing Kwin with wlroots as backend which make this easier as tools which are working with wlroots might be compatible with KDE then. I’m tracking its progress, its quite an interesting approach for sure.
So yeah, Plasma + Wayland = pretty cool & interesting topic but its net ready for people who aren’t ready to bear with some issues & doing some manual work.
Actually it would help a lot of the people using Wayland session would do bugreports on the KDE bugtracker to get help get Wayland viable for daily use 