add an active customer search into long running Journey Orchestrator programs

I worked with a customer who has an interesting use case regarding a long running Journey Orchestrator Program (FkA AO). The main ask was how does JO handle churned customers? Are they automatically dropped, or is there a chance that customers who might churn in the middle of (lets say) a year long Program be included as active participants after they churn?

It presented a unique question, and in discussing this with my counterparts, I do not believe there is any behind the scenes check for "Customer Info != Null and Customer Info:  Status = Active " .  Based on my knowledge of the product churned participants could still be included in a long running JO Program unless a mechanism was included in both the Participant query and between each send step in the JO program (this really only concerns an email chain model). 

In this users case, I suggested that he create a calculated field based off of the Customer Info Object called "Active Gainsight Customer"  with filters for Status Name = Active, and Customer Info != Null. The customer had wait steps configured between each send step - I recommended that he add a conditional wait after the wait to reference his "Active Gainsight Customer" calculated field. Theoretically this should perform an "active customer" check and not allow users from newly churned customers to proceed further in the JO Program.

If there is not any back end "Churn Check" for participants in long running JO Programs, it would be great if we could add a workflow to automate this in the scheduling portion of bionic participant queries. I think this would be very useful for Programs that are scheduled 90 days or longer. Basically, we would add a checkbox to the scheduler that would say something like :
"Long Running Program - enable ongoing Customer Status Check".  If this checkbox was selected - that would add an automatic status check before each send step and would drop participants that were newly churned. 

Is this something that would be helpful? Is there a backend process that already does this that I am not aware of? Would something like this be feasible to look into adding into the product?