The signed system volume is designed to ensure that what's in the volume is not changed. I don't believe it can key the volume to a specific drive.
I used it to rescue a complete working Big Sur install when I was struggling with falling Sabrent Rocket 4 NVMe drives during a new build last spring.
Other success stories: I used it was a couple months ago as way to clone a mixed boot Linux / Windows drive to a larger drive. This involved cloning volume-by-volume, along with using Gparted GUI to create a new drive layout, add a partition, resize partitions, and give partitions their needed flags to better accommodate the existing builds, including EFI / stage2 GRUB, with more room in an existing Windows volume and a smaller Linux. Also, around that time a friend lost a HFS+ drive to corruption that Disk Utility couldn't repair, so used ddrescue to clone whole drive, which revealed there were no read errors, so ran Disk Warrior on clone and it successfully rebuilt the volume and all data was recovered without loss. I've recovered numerous failed systems with ddrescue and can't say too many good things about that program, it's a very valuable tool. Read its docs for amazing usage scenarios, such as reassembling a complete CDROM from multiple spoiled copies, or otherwise merging blocks to repair broken systems.
Great stuff, but you have to comprehend the data structures at the level of what you want to accomplish.
As I said before, a whole device clone is just a device-to-device rescue. If you prefer to image the source as a file on another larger drive, it does this too.
WARNING: GNU ddrescue has no awareness of any higher level structures for the devices. They are just arrays of blocks. What you must watch out for is not letting anything change blocks on the source or target until the clone is completely finished. And you have to consider the higher level implications of the copy. For example, how to increase partition size on target after cloning to bigger drive, how to deal with special partitions such as support the type of drive layout and era of OS, e.g. MBR vs GPT, BIOS vs EFI, HFS+ vs APFS, etc and so on. Oh, and of course do not clone to wrong target.
Hopefully these clues will help you on your way. Please don't forget to think.
Best of luck
