For extreme error logging, you can set –log-file-log-level=Profiling and specify a –log-file, but the log is huge. Even with that, this check is basically a comparison between a tiny SQL query and an enormous one on files. With such a small number, you could probably even go to “Restore from” and form your own opinion, or even perhaps compare it to backups from around the same time (if you have any, and if your file count was stable).
I’m starting to wonder if 2.0.4.5 got better at discovering this issue in older backups. There was another here, along with directions on how to “fix” it by deleting the confused version. Hopefully neighboring ones are good. Deleting a version just means you lose that specific view. Some people routinely set up retention rules to trim versions out of their backups as they grow older. Even after deduplication, this can save some backup space.