Microsoft has MANDATED that all OEMs shipping Windows 8 x86 hardware (which in essence applies to all non-tablet form factors) who wish to quality for a 'Certified for Windows 8' label must provide options to disable or manage Secure Boot.
The only hardware where SB is mandatory and non-manageable by the users are on ARM devices shipped with WinRT. And face it, nobody gives a rat's ass about installing a new operating system on locked-down ARM devices whose OS are so tightly coupled with the SoC used within.
That said, I have nothing but respect for the level of maturity you displayed in handling the 'open vs closed' discussion that spanned a couple of pages. It's very rare to find people who can think rationally and use the best tool for the job regardless of its license.
In my opinion (which is probably worth less than half a cent in a place like Phoronix) there is absolutely nothing wrong with proprietary tools if they are the best choice for getting the job done. My own professor had 'this' to say when I asked him about the feasibility of adopting desktop Linux as a stepping stone to understanding how to manage Linux servers one day:
"That would be silly. Desktop and server Linux are two different beasts, even if they are packaged together in one distribution. Granted you will be able to understand the file hierarchy and some basic commands better than someone else who came from a full Windows background, but that's about it. And ask yourself, is it worth dealing with the potential driver issues for your existing hardware and losing the ability to run Visual Studio and SQL Server, along with many other Windows-only programs? Of course, the call will still have to be made by you, but in my opinion a Windows user with practical experience in setting up a Linux home server and using PuTTY to manage it remotely will beat you in this game soundly."