The EPR contains information such as variable mappings, information that can be retrieved from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following configuration
<bpmToEsbVars><mapping bpm="theBody" esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.