That depends. Are we talking about integrating it into the BABS, or DBS/DES?
Default systems would be very simple. BABS and other custom combat/equipment would have additional considerations, like making the script read modified equipment slots or interpreting weapon types (such as bow & arrow in BABS) and equipping appropriate sub components for those items.
Hypothetically, he could make an 'on/off switch' in the code for end users, but wouldn't implementing it in any fashion require him to make the assumption that the end user isn't using any other add-ons that modify combat or equipment? (Multi-slots, or removing equipment slots comes to mind.)
It's possible, I'm just saying, the likelihood of an end-user finding such a feature practical and easy to modify seems... kinda sketchy.