It's entirely possible to do that, but that's a string that's (often) visible to the user. Now I'd have to remember which "Windows Boot Manager" is Windows and which is Linux.
This is a perfect example of why I don't want UEFI; I spent a long time learning how to do all of this in GRUB, and now they are putting these basic features in the firmware where they belong. Get off my lawn.
Anyway, if this is a problem, you should still be able to use a bootloader to provide the selection menu. I think it should be possible for this bootloader to leverage UEFI to avoid increasing the boot time noticeably. But I do agree that hardcoding names like "Windows Boot Manager" is horrible spec design (and maybe grounds for an anti-trust suit?).
A think I am more open to this type of workaround because I already have set up simmilar systems on my computer. For example, Java does not play nice with window managers that do not re-parent. This caused a problem in Sun's window manager "LG3D", which was non-re-parenting, so they hardcoded a special case for LG3D so things would work. So now, if software asks, I am running LG3D.
You can also look through the Linux kernel device drivers for many special cases.
