Should LDAP verify that user images exist in the Document Library?

Issue

Some user images are missing from my Document Library, but they still have references in the IMAGE table in the database.
As a result, LDAP doesn't re-import the user images during an LDAP import.
Should LDAP verify that references in the IMAGE table refer to actual images in the Document Library, and reimport the images if they don't?

LDAP should not verify that the entries in the IMAGE table reference actual images in the Document Library.

This is because an image only goes missing when the file system and the database are not synchronized, which is usually caused by things such as the manual deletion of files in the file system, or other unsupported actions.
The LDAP import logic references the IMAGE table, and doesn’t reimport images that exist on this table. The system assumes that images and documents in the DB are always in the file system. The File system and DB are synchronized by default when using the supported use cases (delete files using services, staging, etc.).
We are unable to add checks for unsupported use cases for a number of reasons. In particular, scanning the file system and comparing it with the database would create performance issues. Additionally, it is unclear what the best resolution would be for broken references, as it would depend on the use case, which could vary greatly.