Upon further investigation, the only modification was to the lastLogonTimestamp attribute. Since this is a datetime attribute, the import flow is handled by ADExtension.dll (Contributing datetime values FIM Knowledge Bit).
It is not clear what happened to this object to result in the exception on synchronization, but simply disconnecting and re-joining the object naturally resolved the issue.