Similarly powerful would be totally fine. More powerful really is silly. Personally I couldn't make a lot of my workflows work very well with WSL2. Some of the stuff I run is very memory intensive and the behavior is pretty bad for this in WSL2. Their Wayland compositor is also pretty buggy and unpolished last I used it, and I was never able to get hardware acceleration working right even with the special drivers installed, but hopefully they've made some progress on that front.
Having Windows and Linux in the same desktop the way that WSL2 does obviously means that it does add a lot of value, but what you get in the box isn't exactly the same as the thing running natively. Rather than a strict superset or strict subset, it's a bit more like a Venn diagram of strengths.
By default wsl2 grabs half of the memory, but that's adjustable. The biggest pain point I have is to run servers inside wsl that serve to non-localhost (localhost works auto-magically).
I am surprised you had such problems with wsl2 graphics acceleration. That just worked for me, including CUDA accelerated workloads on the linux side.