Why doesn't VBS disable itself after toggling Mem Integrity and Virtual Plataform Machine OFF in 24H2?

Question

I've done everything described in here, it worked in all versions of Windows 11 (22H2 and 23H2), but now in 24H2 it doesn't work.

Normally, it would say "Disabled" instead of "Enabled" after following these steps, but not in this case. I've tried countless things to disable VBS, using Microsoft scripts for it, delete registry keys/putting 0 on them, disabling Tramper Protection then VBS settings, disabling it through Group Policy, everything. Is this intended?

I've tried the following:
Disabling it through Policy Group;
Disabling registry keys based on VBS;
Deleting registry keys based on VBS (as according to MS, it comes as 0 by default);
Using Device Guard and Credential Guard hardware readiness tool;
Trying bcdedit /set hypervisorlaunchtype off;
And different combinations of all the above.

Does 24H2 uses more VBS stuff or something like that? I know disabling SVM Mode would disable VBS, but I don't want to do that since I use that feature from time to time.

I'm using Dev Channel, more specific, 26120.2415 ge_release. If that has any implication with any of this, please tell me.

(Copy of https://answers.microsoft.com/en-us/windowsclient/forum/client_storage-clienttop_virtualization/why-doesnt-vbs-disable-itself-after-toggling-mem/a63a5bdb-e952-41b1-bf70-89a27c6d5fc1?messageId=1d75a523-c555-46d2-95fd-26b49152ccdd)