Me too. I abuse it often as well (hard shutdowns with wsl --shutdown, interacting with files from both Linux and Windows side, etc.). The only issue I have is that because of the virtualization approach it uses more RAM as there is no unified RAM pool for both Windows and WSL (as was the case with WSL1). But that's perhaps expected behavior.
You can still limit the amount of ram used by wsl 2 by setting it in the wslconfig. I like to limit the amount of cores it has access to as well as i tend to find that these two things are generally prone to spiking.