Event target persists not only in child events, but also in father events, too. For example, assume event A calls event B, and an event target is saved there. That event target is not only accessible in event B and further events called by B, but also in event A (after calling of B, of course). And if event A calls event C later, that target is accessible in C and its children, too.
The conclusion on Weedes' event, though, is unchanged, as multiple copies of event there is independently triggered by MTTH. So no interfering there.