The issue with Big Sur and beyond is that Apple has shut third parties out of making bootable system backups by introducing a signed system volume. CCC and SD can *facilitate* a bootable backup, but neither can create it directly, no matter how anyone chooses to spin it. We were able to create a bootable Big Sur backup almost from day 1 (long before SD) because we had heavily experimented with ASR and already had (previously rejected) code that we could drop in.
Here's from our blog: "All on its own, Big Sur introduced a significant new change to the creation of an external boot device. The operating system now resides on a cryptographically sealed "Signed System Volume" that can only be copied by an Apple-proprietary utility, "Apple Software Restore" (ASR). We were already familiar with ASR, so fairly quickly we were making bootable backups of Big Sur back in November. It hasn't been perfect though. We've performed tens of thousands of ASR clones at this point, and we've discovered that ASR is just not as robust as our own file copier. There are many scenarios where ASR simply fails with no explanation. ASR is also very one-dimensional; choosing to copy the system requires that we sacrifice other backup features, e.g. we cannot copy the system and retain versioned backups of your data, we can't evaluate what was copied, we can't exclude items from the initial backup, we can't save checksum data for later verification. So, while we're certainly able to make a bootable copy of the system with ASR, it starts to feel like using it causes us to lose sight of what's actually important to back up – your irreplaceable data."