This isn't like an operating system where backwards compatibility takes effort. Since this sits on the boot path, it takes more effort to remove a wart than to just leave it.
I know us developers like to ask "why not fix the wart", but that wart hurts no one.
https://www.os2museum.com/wp/will-the-real-real-mode-please-...
Only the BIOS init code cares about which mode the BSP starts in
But the OS cares about what mode the APs start in. Most operating systems use INIT-SIPI-SIPI, which starts the APs in real mode.
If an OS uses ACPI 6.4 Multiprocessor Wakeup Mailbox instead, then UEFI does the INIT-SIPI-SIPI on the APs, puts them in 64-bit long mode, then hands that to the OS. However, few bare metal UEFI implementations actually implement it, it is mainly implemented by hypervisors to support confidential VMs.
So, Intel/AMD could make the BSP start in 32-bit protected mode, with minimal BIOS code changes; but the APs would still need to start in 16-bit real mode. They couldn't make the APs start in a different mode until they got everyone to move off INIT-SIPI-SIPI.