There is a second workaround for this issue, which works in DPM 2025, 2022, 2019, etc.:
Run the command the specific replica that is causing this error, then it will crash the DPM console if you have it open and force your PowerShell window to close. This is okay for purposes of this workaround.
If you run that command from Windows Terminal, then the terminal will error with a generic "code 2." Again, for this workaround, this is okay.
In either case, simply reopen PowerShell/Terminal and run the command a second time, again specifying the replica in question and it will eventually get copied.
Once the copy succeeds, run your Consistency Check again and it should succeed without going "inconsistent" with the ID 40002 error.
It's a bit of a jank workaround, but it sure beats having to restart the whole server every time you get a single ID 40002 error for a single replica.