I have now seen what this seed device corruption can look like, and I can say with confidence that it could not have caused the issue that prompted this thread.
If people are able to reproduce seed device related corruption in DeviceDiscovery.properties, then they should start a new thread with the exact steps needed to trigger the corruption.
