EX Option With Non Ethercat Interface

Will the EX option cause problems with a CtrlX drive if we don't use Ethercat?

Obviously the drive connect app won't work, but can we ignore it if we don't want to use it?

 Reason being...

I have an existing serial machine that currently uses sercos line topology with an Indradrive/KCU powering some indradrive MIs.

We are considering converting the Indradrive/KCU to XCS/XCU going forward now that Indradrive HCS02/HC03 is being phased out.

We are not sure if we are going to convert the existing XM controller to Ctrlx Core/other ethercat/EithernetIP master yet, so we are considering putting the EX option on the XCS in case the controller switches to a 3rd party ethercat controller that has bad EOE/ADS support later on down the road. 

This would give us the following potential architectures:

 1: XM to XCS via sercos (EX option would not be of use, but no major control/PLC changes)

2: Ctrlx Core to XCS via Ethercat (EX option would not really be needed because Ctrlx already has EOE/engineering communication to the drives onboard/downstream. HOWEVER, PLC code needs to be rev’d so some risk associated with this approach).

3: 3rd Party Ethercat master to XCS (EX option could help here, but full on retrofit of controls/PLC code)

4: 3rd Party EthernetIP master to XCS (EX option would not be of use, but full on retrofit of controls/PLC code)

So basically, I need to know if the XCS will function properly if the EX option is equipped but we don’t need to use it due to sercos/ethernetIP/non-Ethercat master.