Reference UUID Synchronization

I've written a module that maintains relationships between a node and all of its "reference fields" across multiple Drupal instances, based upon the UUID of the referenced entities. The "Node export relation" module didn't quite cut it for me (even after modifying it), and I never found anything else that seemed to fit the bill.

I'd like to share this via a Drupal project, but first wanted to check if the module is actually useful, and whether it doesn't overlap with another one (didn't really find one that truly covers the same topic).

The module roughly works like this:

• for each "reference field table" (ie: "field_data_field_..." and "field_revision_field_...") an extra "reference UUID" column is added next to the "reference ID" column
• when creating or updating a reference,
  • we check the "reference field value array" (see below for what I mean by that)
    • if a UUID is available, we don't trust the NID/TID and either resolve it via the UUID or set it to NULL to resolve it later on
    • if no UUID is available, we assume we can trust the NID/TID to be correct and resolve the UUID via the NID/TID
  • we run over all other "reference field tables" and try to resolve any existing NULL references given the current UUID and NID/TID
• when exporting nodes we make sure the UUID of each reference field is added to the export

The hooks we use are:

• hook_node_insert()
• hook_node_update()
• hook_taxonomy_term_insert()
• hook_taxonomy_term_update()
• hook_node_export_node_alter()

The "reference field value array" I'm talking about looks like:

In the end, when this module is enabled, I can import nodes and restore all references

• when performing a clean install via a "node_export feature" included in the install profile
• when importing via the Feeds module (requirement is that the UUID value for each reference is passed in the XML and parsed/processed correctly)

The only issue I currently have with my solution, is that during "insert" and "update" the performance may be influenced by this module. However, my current project isn't too "CRUD intensive", and viewing nodes doesn't get influenced, so it's really not that big a deal.

Now, for my actual question: does this module make sense, or is it something that's already been covered by something else? Or am I missing something (obvious)?

I'd be happy to share my code, but first wanted to make sure it's really worth it...