For most, running a manufacturing business means that they do repeat runs of a production schema to execute production runs. This means that the production run is defined by the production schema (or in OFBiz parlance: the routing). And each production schema is defined by its associated schema tasks (OFBiz: routing task) and other elements.
In this construct the associated schema tasks have a lifespan (fromDate and thruDate fields). This should ensure that a new production run isn't build with tasks from a schema that has tasks outside of the intended sweet-spot.
This, however, poses unnecessary constraints in the situations where the initial production run is based on an existing schema and then gets enhanced with additional schema tasks.
To this date the list of available schema task encompasses all. So, in that respect a statusId value that would limit the list of available is warranted.
However, this kind of work effort definition also has to adhere to a lifespan. IMO, this should be the first way to show visibility for direct selection.