My experience with that is that 100% CPU can happen if the WSL2 image is using more memory than available, and is then swapping. You should be able to check that by looking at the VmmemWSL process. There's also an option in the WSL config you can specify to limit the amount of memory it can use.