Dependency Behavior When Downstream Tasks Are Completed

Our projects are created from templates that have all dependencies mapped out (Think X -> Y -> Z).

Occasionally a project does not require Task Y, so it is marked ‘Non-Applicable’ (which is a completed status).  [It is not desirable for our teams to delete the task and reset dependencies]

If Task X then has its timeline extended, Task Y does not reschedule because it is in a Completed Status Group.  Task Z also does not reschedule, because it is dependent only on the previous task (Task Y) for its schedule.

I would like to see logic put in place that when a task(s) and/or subtask(s) that has Active dependencies before and after in a dependency chain, the ‘dependency requirements’ are set based on the Active dependency.  [A>B>C>D; when B and C are marked NA, D should become dependent on A]

Implementation Though: I am sure there would be situations where the described behavior here would not be desired.  With that in mind, it would be interesting if this were an optional attribute that could be activated within Custom Workflows.