I think it's not the GUID, but the fact that referencing the GUID is the only way to get at the functionality any more.
Yes, your devices and various other underpinnings have GUIDs, but very few of them _only_ surface the GUID as a referent to the thing in a place a user would have to access it.
Similar to how, if you could only get at this by doing "rundll32 shellex.dll LoadOldPrinterSettings", the issue wouldn't be a function named LoadOldPrinterSettings, the issue would be that it's making you reach into a DLL to invoke a function by hand to get at it at all.
Yes, your devices and various other underpinnings have GUIDs, but very few of them _only_ surface the GUID as a referent to the thing in a place a user would have to access it.
Similar to how, if you could only get at this by doing "rundll32 shellex.dll LoadOldPrinterSettings", the issue wouldn't be a function named LoadOldPrinterSettings, the issue would be that it's making you reach into a DLL to invoke a function by hand to get at it at all.