Musescore plays noise everytime I open it up (using Voicemeeter)

That's it, that's the issue. Have tried reinstalling, changing settings to default, checking synthesizer, downloading a Musescore General HQ complete copy (since the app itself would never download it completely). Nothing will make it sound right.

1) I'm using Voicemeeter Banana (with no exclusive control on any device whatsoever), and I think this makes Musescore crash everytime. I'm now "solving" the issue by putting an entirely random entry on WDM-KS API (currently labelled as "CABLE Output" but actually sounding through "Voicemeeter VAIO". I've checked my sound configuration. There's no mislabelling or any weird routing.). It doesn't make any sense. All other apps can work fine with Voicemeeter.

2) What's the problem with Musescore? Why can't it fix its audio to AT LEAST not have that annoying noise everytime it can't handle more than one audio driver?

3) I've tried every solution on https://musescore.org/en/node/96811 , and as you can see, no one has worked, except for the random input I used*. Please don't lecture me on "Be sure to try all of the suggestions", because I have done that.

4) Musescore 3.6 , Windows 10 (64 bit). When reverted to factory settings it switches to MME Voicemeeter (I think, I won't do that again since it could flip everything back to noise again and who knows what route should I take this time. I'm sure it was MME though).

5) Please fix this bug. Every app that uses audio in any form has done it, I really don't know why Musescore should have such a terrible audio interface.

*For those who are not familiarized with Voicemeeter, it works through an ASIO API. The audio should render through ASIO, but it won't unless I use WDM, and even then Musescore won't follow the exact route I give it.

Attaching current file I'm working (don't know how it would help but well).

Note: Have seen here https://musescore.org/en/node/284568 that Musescore changes the latency when opened. Is that a thing for other OS beyond Linux? If that's the case, how do you do a "PULSE_LATENCY_MSEC=30" on Windows? In my case it would have to be 32 msecs, since that's the general latency with a 512 buffer size (on WDM).