How did you make your "clone"?
There are various ways this can break macOS due to Catalina APFS installs having been migrated to the Sealed System Volume, which places the installation in an APFS container and divides the installation into a pair of partitions: "Macintosh HD" and "Macintosh HD - Data". The first one is the SSV, a crypto sealed form of the stuff (roughly) thought of as protected by SIP, but this isn't controlled by SIP; it can't be changed outside of a process running code that is authenticated all the way to Apple certificates. The "Data" part is where Apple apps that can be updated incrementally go, plus all the user data, and 3rd party apps. These two area are combined using black-magic of APFS firm-links, which present a namespace that looks like a single volume.
These two parts have to stay in sync or trouble ensues. A special Apple tool called APFS Replicator can clone the whole shebang, and as long as no Apple updates are applied. APFS Replicator requires erasing the target drive.
For a source and a backup at a given fixed version of macOS, the source Data part can be incrementally updated and copied to the matching backup drive, and the backup will work. But if any system SW update is applied the the source drive, this resets the seal and the only way to update the full system backup is using APFS Replicator, which necessitates erasing the backup. If only the Data partition is cloned to the backup, the linkage between the Data part and the clone SSV ends up out of sync and trouble ensues.
For these reasons and more, traditional incremental cloning can't work. A full block-level copy of the entire drive can work because it doesn't disturb the crypto seal. — I am massively waving my hands here; I'm not an expert and I may be wrong on this last point because Apple has been doing a lot of work on this over the last year, but you get the gist. WARNING: When using a block-level clone, I have seen Disk Utility get wildly confused about which part goes with which drive's macOS container volume, presumably because UUIDs are being reused... Fair warning about data loss due to such a mess.
This is why a recommended approach to system maintenance is to install macOS then use Migration Assistant to merge your data.
Your screen shot shows that the volume is ok, so please review your approach to cloning.
One more thing, after a APFS Replicator clone, renaming the target volume doesn't update a key file used by bootloaders to present the volume name in the boot list, so if the source and clone are attached at the same time you can't tell which is which because the clone had the old name. I can post the fix if anyone cares.
