I have never heard of that potential until now, but that’s quite annoying if true.
My idea for a workaround is to prefix the versionstamp with a counter that represents the version of that installation of the database.
So if you choose to use a 1 byte prefix, you have 255 cluster re-installations if you increment that prefix upon each re-installation as a part of the bootstrap process after restoring the data, but before starting the application.
e.g. LogName-Prefix-VersionStamp => Value