I don't follow you.  The ID in question here is not filesystem dependent, like a UUID or a label is -- it is in fact tied to a device, and the only way to add it after the fact would be to update the low-level device driver that handles it to start providing the device ID (not likely, they all already return one if it is present), or for you to upgrade to a new version of udev that adds support for a block device type it did not already know about.  Given that our ids ultimately come from ata_id or scsi_id, I do not see them as changing once defined.