For them to call it Bootcamp 2 (a "product" per se), they'd have had to have another OS they could actually demo installing. Otherwise "Bootcamp 2" is just a mysterious empty chooser window.
But at the time there was nothing, because Apple Silicon wasn't a platform anyone but them was targeting, because they had just created it.
So they built the infrastructure, and then waited for someone to actually start taking advantage of it, before bothering to acknowledge it.
And because that "someone" isn't a bigcorp (i.e. Microsoft) wanting to do a co-marketing push, but just FOSS people gradually building something but never quite "launching" a 1.0 of it — Apple just "acknowledged" it quietly, at developer conferences, exposing it only via developer-centric CLI tooling, rather than with the sort of polished UI experience they would need if Microsoft was trying to convince Joe Excel User to dual-boot Windows on their Apple Silicon MBP.
> announce « The most secure Mac ever » silently releasing with closed bootloader
That's extremely unlikely to happen, as Apple's hardware and OS developers build Macs and macOS (and all the other hardware + OSes) using Macs and macOS. And those engineers (and engineers working at Apple's hardware and accessory manufacturing partners) will always need to be able to diddle around with the kernel and extensions "in anger" without needing to go through a three-day-turnaround code-signing process.
There's a whole proprietary, distributed kernel development and QC flow for macOS, that looks a lot like the Linux one (i.e. with all the same bigcorps involved making sure their stuff works), but all happening behind closed doors. But all the same stuff still needs to happen regardless, to ensure that buggy drivers don't ship. Thus macOS kernel development mode being just one reboot-and-toggle away.