Problem solved
I have THE solution. No guarantees are given, but I'm quite confident that this will solve the issue, at the very least, on Windows 11 virtual machines, and, presumably, in qualifying earlier versions of Windows as well. This is what I did.
- Shut down the Windows virtual machine.
- Within the Parallels Desktop Control Center, locate your Windows virtual machine Configuration (cog icon). Select Hardware. If you see a "TPM Chip", remove it.
- Using Finder, locate your Windows virtual machine (.pvm extension). Right-click it and select Show Package Contents.
- In the new window or tab, right-click on config.pvs, choose Open With and select TextEdit.
- In TextEdit, search for "<EfiSecureBoot>". Presumably, a non-zero value will be displayed immediately to its right. Replace that value with a zero. Save the altered config.pvs.
- Start your Windows virtual machine. It will probably take longer than usual.
- Cause Windows to check for software updates. KB5012170 will be one of the updates being offered. Install it. It will succeed.
- Shut down your Windows VM.
- If you removed a TPM Chip in step 2, reverse that action. In other words, add a "TPM Chip" to your virtual machine configuration.
- Re-open config.pvs using TextEdit, search for "<EfiSecureBoot>" and replace whatever number is to its right with "1" (without the quotation marks). Save the file and quit TextEdit.
- Launch your Windows VM.
- Done. KB5012170 will appear among the installed updates if you choose to display the Update history.
Unfortunately, this doesn't solve the Core isolation Memory integrity issue.