This is just something I have wondered about for a few years without articulating it.
I have found that testing on a virtual machine bears very little relationship to the results obtained and the bugs/difficulties when installing onto bare metal. The vagaries of many different hardware combinations just preclude the smooth and simple experience with a virtual setup.
I have found using a bootable usb stick with persistence offers a window into how a new o/s will perform on my hardware, but that’s really only good for an Ubuntu based system.
Ahh, that is probably the reason I find such difficulty with testing new distros, that isn’t something I concern myself about; I am always most interested in seeing how a new distro reacts to my hardware, and software Mythtv etc. Also attempting to get my head around using pipewire instead of pulseaudio. The latter is important because I have reduced hearing and need to use headphones a lot. Unfortunately it is an absolute nightmare trying to consistently get my Sony bluetooth headphones working simultaneously with speaker output so we can enjoy watching Mythtv together. No sooner do I get it working then the next time I boot up it doesn’t work. Why oh why do they remove a working system such as pulseaudio before it’s replacement is fully operational? Linux does this time and time again, the devs just don’t seem able to learn. Same with snaps and countless other instances.