The sizes of the damaged files are suspiciously binary (pasted some into Windows Calculator in Programmer mode), many are 4 KB multiples (making me think Windows cluster size or 4 KB drive sector), but at least one wound up not a multiple of 4 KB but a multiple of 512 bytes (drive sector?). I didn’t look at ALL the file sizes…
Windows efforts to repair a filesystem might cause chops at cluster size boundaries, but that 512 puzzles me.
File names and sizes are often logged when files go to the backend, If you want to look for the original view…
–dblock-size defaults to 50mb, so dblock files of that size would be normal for a substantial backup increment.