Following are some questions related to tampering scenarios.
You can remove the SnapLock license. however, files that are already in the SnapLock state retain their immutable WORM protection. The only disadvantage of removing the SnapLock license is that you can no longer put new files into the WORM state, or create new SnapLock volumes.
No, file deletion is not possible on a Data ONTAP release that does not have a ComplianceClock. The ComplianceClock is a secure time base that can be initialized only once. The ComplianceClock is immune to tampering with the system clock.
No, each SnapLock volume has a unique UUID, which is typically tracked by the archival application, or as part of the company's archival policies. A new SnapLock volume can never re-create the unique ID of the original volume with incriminating records, thus defeating any spoofing attempt.
You can move the volume, but you cannot reinitialize the ComplianceClock. If the ComplianceClock is already initialized on the system, but does not match the ComplianceClock stored in the volume that you have moved, the least of the two will be used for determining expiration.
You do not need to fix this issue because the ComplianceClock catches up to the system clock at the rate of one week per year. This is to prevent any tampering with the retention date.