Repair usually just confirns local database and remote file lists / hashes match, but it doesn’t check actual backup files (that’s what Verify does).
It’s possible the remote dlist / dindex files also have the “problem” so repair doesn’t detect it and recreate just makes a new database with the same problem.
If that’s the case, then a recreate after removing some of the files from the destination should resolve the issue. BUT, that is a last resort.
Perhaps @kenkendk could glean something from a database report?