That is really the difference between Win 10 and Win 11: Requirement for UEFI, TPM 2.0 and a CPU that does AVX2 and FMA3, and some kind of hardware-assisted virtualization.
UEFI allows them to rewrite their entire bootup codebase with only one target. Literally hundreds of megabytes of sourcecode will be removed from their tree, some of it dating back to the 80's, and replaced with something that is much, much smaller and cleaner.
TPM 2.0 and hardware-assisted virtualization allow them to move the kernel one level up in the privilege hierarchy, while properly verifying it during boot to eliminate entire categories of exploits and providing trusted computing that might actually work this time. (Not entirely positive, but it's a desirable feature for them.)
And having all the cpus that can support the OS also support the good vector instructions greatly raises the baseline against which most software is compiled. This is an often underlooked point: The benchmarks and the most performance sensitive programs might get multiple code paths or versions for different cpus, but by far the most software made for Win 10 still only targets a very low baseline. Even if it's not 32-bit, most programs only target the ancient SSE2 (!) because that's the baseline that's quaranteed to exist if you have a 64-bit cpu, never mind it's over 20 years old now.