Why does ddrescue not use distinct mapfiles for read and write errors? (And how to detect write errors?)

Sometimes, I have to clone a hard drive to another one that seems healthy (SMART values OK), but whose surface could not be checked fully for possible bad sectors. Typically, if I clone a healthy hard drive, I might use a destination drive that was not previously wiped and, accordingly, not fully checked Please let me know if I'm wrong: **I believe that ddrescue only reports read errors.** This also means that ddrescue would indicate a successful cloning without error, even if some sectors could not be copied to the destination drive because of write errors. The same way, the mapfile does not let you know if there are errors on the destination drive. So, I always wondered why does ddrescue does not let generate two map files (read.log) (write.log), and I assume the short answer could be "This was not implemented yet.". This leads to a second question: is there a way to detect write errors? N.B. I assume computing checksum on two 1TB drives after the cloning would take a while. Is there a better solution?