But conversely, with two implementations you can change one if needed without affecting the other.
I've had this happen a few times, you DRY an abstraction and then discover that the cases you thought were the same are slightly different. Now you have to add parameters or logic and change or at least test everything it touches.
this is my main point, yes.
N (initially) copied implementions does introduce the risk of 'forgot to update this one' bugs, but these bugs are about as simple as it gets to find and fix.
Abstractions on the other hand introduce the risk of 'what random thing am I going to break by changing this?' bugs which are typically much harder and more time consuming to find and fix. Further, the risk is recursive, as the fix might break yet another thing.
I'd maybe agree with the gp that instances of the former are as common as the latter. But to my original point, they just waste far less time.
I certainly know which class of bug I'd prefer to have to fix in a hurry, like a production incident, for example.
If you have good taste in abstractions, fixing a bad abstraction is usually just copy/paste/rename/modify.