[[ How is the recovery partition different from a bootable partition? ]]
The recovery partition quasi-boots the Mac.
That is to say, the Mac is booted, but you don't get to the finder and you can't access anything or do anything other than the limited options that the recovery partition provides.
With a fully-bootable partition or volume (such as one created by either CarbonCopyCloner or SuperDuper), you have "full control" of your Mac, just as you would have from an "internal boot". You're in the finder. You can manipulate files and folders. You can run any app you want.
Why would anyone want the "half-boot" the recovery partition provides, when you can simply clone a drive, and have a full boot instead?
To answer my own question, it's probably because of the belief that "if Apple included it to be used as a backup tool, it HAS to be the better product". 'Tain't so.
I've seen post after post after post after post after post from users in this forum, who try to boot the Mac, and can't. They're wondering what to do next. If all they have is a recovery partition to work with, their options are limited. If Disk Utility's repair function doesn't work, about the only choice they're left with is to do a complete system re-installation, and/or a complete data re-installation using Time Machine.
If they could boot from a clone, things might go much easier, with MUCH less work.
I've seen instances on my own Mac where something like a finder pref file became corrupted -- Mac would kind of half-boot, but couldn't get past the grey screen when the finder reads its prefs and then loads.
Just "booting externally" could correct this. Open internal volume, trash finder prefs, restart. Easy as pie.
For the user with only a recovery partition and TM backup, this would be a long, arduous process. The recovery partition gives no way to trash a file, and the user would have to do a complete system re-install to get a workable finder again.
I've had an instance or two where the Mac seemed to hang while booting from the internal drive. In those cases, all it took was an "external boot", then a re-boot of the internal, to get going again (whatever it was, I never found, but an external boot fixed the problem right away).
No one who owns a Mac should be without a second, fully-bootable backup.
I can't understand why Apple didn't provide the option within the TM framework for a user to do a "full clone" as well as a TM backup.