This'd be a cool feature. It has been discussed a little here.
Trouble is, it can turn into a bit of a rabbit hole. Potentially you could limit it to just animCurves.
But what if you had some other node connecting to your Ziva node. Let's say it's the outValue of a remapValue node to the excitation attr on a zFiber. Or maybe it's a blendColors.outputR going to inertialDamping on a zTissue. And then what about the nodes that feed into those nodes. Then it has to support serializing to disk. You can see where this goes 🙂
Perhaps supporting animCurves but nothing else would be ok? Would this be consistent enough? or possibly confusing to users (i.e. why some nodes are supported but not others)?
For a while there I had a tool that built on top of zBuilder. So I could populate an object that would remember the name of the connections to ziva nodes, but not store any of the other data. That meant that if it found the source of the connection again on the rebuild, it would automatically make that connection again. There's additional work that needs to be done though, because when you delete a node with connections in Maya, you lose the connecting nodes as well, if there's nothing else connecting to them. So you have to do a 'safe remove' where it breaks the connection before deleting the Ziva node.
This stuff is tricky! 🙂