If I wanted to do this I would consider developing a Conditional Node expression to loop through the affected objects in a Change Request/Notice and determine if it is in the Resulting Objects of another Change Notice and then route to a human for resolution.
But the question is do you want to prevent it? Arguably, if there are additional Changes coming in you would want to consolidate as much as possible and incorporate in an open Change if possible. Any of this would be a change in scope of the Change Notice being implemented and may impact Effectivity, schedule etc. Adding in a spelling correction on a drawing where other modifications are being made is probably a no brainer but what if it means a tooling modification and/or planned production?
I would think each case is best evaluated indivudually to determine if adding on to an existing Change Notice is appropriate (by Revision maybe?) or if a second follow-on Change Notice is more appropriate.