It doesn't directly say why that requirement was introduced, though one could gather from the context that it's being done for security. But perhaps more interesting is that both this presentation and the MSDN page you linked also talk about enterprises being able to control what runs on the hardware themselves. Your MSDN page has:
>Removing Microsoft UEFI CA from Secure Boot DB provides full control to enterprises over software that runs before the operating system boots.
... and the presentation has:
>Security Certificates added to my device are documented and justified, with a pre-defined security response plan.
So I wonder if the reason is just "We wanted to make it convenient for enterprises to not have to do a pre-provision step to remove the UEFI CA, so instead we mandated OEMs to not enable it in the first place."
It would be extremely silly if that turned out to be the reason...
[1]: https://uefi.org/sites/default/files/resources/UEFI_Plugfest...
If MS's distrusts its own ability to vet other people's code, why trust their ability to vet their own code?
If you want to do the legwork yourself, feel free to roll your own PKI and sign things you trust yourself.
It has been documented for a while really:
https://docs.microsoft.com/en-us/windows/security/identity-p...