The ECOM100 is a LEGACY product. When used with Do-more CPU, external clients can read/write to DLC, DLV, DLX, DLY (legacy DirectLOGIC data types that are supported in a Do-more PLC). H2-ECOM100 does NOT know about Do-more's MHR memory (or R or D or even X, Y, C, but ECOM100 DOES know DLV, DLC, DLX, DLY but as the old DL octal V, C, X, Y). The ONBOARD Ethernet port of the H2-DM1E (controlled by the Do-more firmware) DOES know about MHR (and R, D, X, Y, C).
You are actually close to making it work for your "company data collection" network. Basically, in your 260 CPUs, you are copying your "modbus" data into 260 octal V memory addresses that map to Modbus Holding Register addresses. DO THE SAME WITH DO-MORE, except instead of copying it to MHR, put it to the proper octal DLV memory in Do-more.
Since you know about the "spreadsheet from heck" that maps the Modbus addressing to the octal V memory of a 260 - USE THE SAME SPREADSHEET MAP for DLV (e.g. a Modbus Holding Register that maps to V2377 in a 260 would map to DLV2377 in Do-more).
If your "company network" has access to the PLC via the control network on the ONBOARD Ethernet port (not a good idea), you COULD use MHR, but using the Onboard IP Address, not the ECOM100's IP Address. But you probably ISOLATE your CONTROL network for your pneumatic controls, and use the ECOM100 for the "company network". Hence, you need to stick with my first answer and use DLV and the "spreadsheet from heck".