What about a virtual cape EEPROM file

So in working through the capemanager, device-tree concepts, and the syntax of the dts files it kinda appeared to me that the EEPROM data structure is pretty straight-forward and if I understand the process correctly, when an EEPROM is found and the data is read the pin mux settings are all handled automatically according to the data read in. So… why not be able to drop a file that contains the same data into a directory and have that searched as well as the I2C bus? Then it’s very simple (relatively) to pump out a file that sets up the hardware the way it needs to be without getting into editing and compiling the .dtb files.