When linking, symbols pointing to addresses are involved. The main program calls functions in the library, and you end up with a whole program. On the other hand, a bootloader just does its thing and then jumps to a fixed address in the main program. The main program doesn't call anything in the bootloader. (Note, the Linux kernel has a special clause that explicitly allows the userland to programmatically interface with the kernel.)
I realize this sort of depends on the microcontroller toolchain. I'm familiar with a few, but not much with STM32 stuff. If the toolchain is dumb and implements the bootloader in a way that resembles linking, i.e. making it possible to resolve all the symbols in the bootloader from the main program then it could very well make the bootloader subject to the GPL.
This makes 0 sense as presented here. The GPL explicitly distinguishes mere aggregation from combining in a way that makes it a larger program. Putting both the proprietary bootloader and the GPL OS on the same disk / in the same system makes 0 difference to whether the bootloader is covered by the GPL or not.
If this were true, then any phone, any PS5, any Linux laptop, and almost all consumer hardware would be in violation of the GPL (note that the wording quoted there is also part of the GPLv2, it's not GPLv3 specific).