Normally we discourage people from tinkering with their database but this is a pretty benign change. The scan configuration name is only found in the scan dbo.ScanConfigurations table.
The key is to make sure the ConfigurationName is unique. The only area I can think of that would be affected by this change is if you were generating asset reports based off of a scan name. Those templates would need to be updated.
I always tell my customer to do it like that:
New scan --> select existing scan --> assign new name to the scan
After that, delete the old one.
This way is fully supported and works fine, but all the old content will be deleted.