Resource GUIDs when an asset is originally created are some kind of hash of the unique path to the file. However, if you rename a file within workbench, this is never recreated. This is probably done to avoid having to walk through the project assets to modify each config/resource which references the original resource, however, there are some issues this causes.

For instance, if a user creates a version of an asset, then renames that asset and decides to start with a new version of that asset, both will have the same GUID.

When the GUID is changed workbench will obviously have to fix all of the assets that pointed to the prior GUID. This problem could be made easier by making a hash of the asset file itself accessible in the .meta file (concept pictured below) and looking for mismatches.

MetaFileClass {
 Name "{D7B2D0DAA40C67BB}test.conf"
 LastHash "E225722CFDB575FB"  // Use this for ensuring the resource we are getting is what we actually want
 Configurations {
  CONFResourceClass PC {
  }
  CONFResourceClass XBOX_ONE : PC {
  }
  CONFResourceClass XBOX_SERIES : PC {
  }
  CONFResourceClass PS4 : PC {
  }
  CONFResourceClass HEADLESS : PC {
  }
 }
}