"A copy which can be reached by the same mistake isn't a second copy. It's the same copy with a delay" sums up the night better than any diagram. The part that hurt to read was the nightly job reporting success for months while a whole branch of the tree had been skipped since a permissions change, and fifteen minutes a month of restore testing is a cheap price for catching that.
That silent-success problem shaped a lot of how we built CleanSync at Ascendra Ventures. It keeps Google Drive in two-way sync with a server you own and keeps a copy of every Gmail message outside Spam and Trash, with rclone moving the files underneath. Before the first sync it shows what exists only locally, only on Drive, and on both with differences, and waits for a typed confirmation. After that, every sync is rehearsed as a dry run, and if one would delete more files than your limit, it stops and shows you the list. None of that replaces a restore test, but it does make "completed" mean something more specific.
After the offsite copy turned out to be too slow, did you start measuring restore time on a schedule, or only test it that once?