In my mind each .ESP should only have it's own CTDA references, which get tacked onto the end of the list. After all, the rule references a global FormID so this should be causing a conflict winner/loser condition. Could this have been avoided by using de-isolation or should I just go ahead and use Tes4Edit to remove any rules except those related to the mod .ESP.
I'm not really finding specific guidance on cleaning for this scenario. My rule, with the inherited rules, is not identical to master so it doesn't have any automatic cleaning options. Using a "Quest Data" rule to filter "Generic" Dialog in reference to NPC's, Races, Factions, etc. seems to be common practice so I'm certain each successive mod must tack it's rule onto the end, or else there would be total anarchy.
Anyway, I appreciate your time, and any replies.
Note: I think my reasoning is wrong. In CS you always add a new rule to the existing list. Removing an existing rule would create a deletion record (in the .ESP relating to the master) as now I am changing the master. In fact that would be the only real danger. I think Tes4Edit is just showing my rule in relation to the parent's - nothing is really added to the .ESP.