That's right... if you can get to it in the Finder, of course!

With the reverse, you'd want the backup to be named the same as the original, restored to the original drive name. That's the best way, at least...!

Not sure what you mean by that..
Even if the primary boot volume is hosed we could still boot from the clone and rename it to match, right?

I keep two full clones on two different drives. Currently the clone volumes are named "Backup1" and "Backup2". It sounds like I should rename them to match my source volume...

The clones would mainly be used to to a full restore back to the main drive in the event of a major system problem.
Of course occasionally I need to mount the drive and grab a single file.
And sometimes I need to boot from the clone and work from it for a little while.

This seems to point towards the 'same name' concept, rather than the Backup1/Backup2 that i have been using...

Well, you can see if it makes a difference for you, actually. It might not, especially if you hold down Shift when you boot, because any applications that have this problem wouldn't run, and as long as the original volume is named properly, you'll be OK.

Again, the main issue here is applications that store aliases that might resolve to the original drive. If the original drive isn't there, it's not a problem, because the aliases will "fix themselves" if they can't find the original file.

But -- if the applications that make reference this way don't start, the aliases don't try to resolve, and the problems don't occur. See what I mean?