I don't like it ... in the sense that it is not a good solution.
But I do like it: It is a decent solution, and at least you're trying to make backups.
Why isn't it a good solution? It requires too much human intervention, you have to move disks back and forth, you have to type too many commands, and those commands have to be run as root. There is too much potential for mistakes here, and given that mistakes might be "pull the wrong disk out" or "type a command wrong as root", that's just too dangerous for my taste.
Here would be my suggestion: Don't make the second disk a mirror. Instead make it a second file system, and update it with ZFS send and receive, or with rsync. And try to set up the permissions so the process of backing up is NOT CAPABLE OF modifying the live disk. How you do that depends on your usage, your requirements, and what workflow / software you want to use.
To the point that "human mistakes are dangerous": My previous employer (IBM, at the time the largest computer company in the world) actually did accurate studies of what causes data loss on IBM-serviced storage systems. And the absolute largest contribution was human error. With the classic example being: The hardware of a storage system (which is in practice always using redundant storage) reports a disk failure; the system continues working fine due to redundancy, and a field service technician is sent to replace the failed disk. The service technician arrives, promptly pulls out the wrong disk (the one that is still working fine and contains good and valid data), throws it in the trash (as he should), leaves the dead disk in the system which is now down and has suffered data loss, and happily leaves and drives to the next customer. Big oops, but happens all the time. The fix? Very clearly labeling and numbering the disks and the slots they go into (with big letters or numbers); adding blinking lights so the good disk has a nice green light, and the dead disk has an angry flashing red light; giving instantaneous feedback, if you pull the wrong disk the system immediately starts beeping and the lights start flashing blue and red; and lots of training and attitude adjustment. And making it so less maintenance is requires, since every maintenance operation has a high risk of mistakes; one example is called "fail in place", leaving dead disks in the system, so there is no chance to remove the wrong disk.
In turn, this leads to the old joke: To administer a computer, you need to hire a man and a dog. The man is there to feed the dog. The dog is there to bite the man if he tries to touch the computer.
So the moral of these jokes: Think about how to simplify and automate your workflow, and reduce the risk of doing the wrong thing, like mirroring from the backup disk (which has outdated information) back to the live disk.