Yes. From a computing freedom point of view, the only way I have freedom over my computing is if I control the code that's running on it. If I'm running code that I don't have source for, I don't quite control it as much as I'd like to. But if
someone else is running code that I don't have source for, I sure as heck don't control it!
Running a closed-source bootloader on a platform with firmware enforcement of signed bootloaders is not good. But the problem is not the signature requirement, the problem is the closed-source bootloader. The signature requirement is only a problem in the case where (as on Windows-logo machines running ARM) it requires you to run a closed-source bootloader, or even an open-source one that you do not have the ability to make changes to. If you want to ensure your computing freedom, the best thing to do is to have your firmware ensure that you and you alone, or someone you trust and them alone (e.g. a vendor of a free OS that you think is reputable), can boot code on your computer.