I don't think my current org is crazily complex, but we already have many automations on various objects. Having one flow per object, even just for when records of that object is updated is restrictive because it means if one sub-flow under the master flow fails, all other sub-flows will fail since they are in one transaction. I think restrictive entry criteria, Flow Order of Executive, Flow Explorer and Flow Orchestrator took care of the question One Flow or not to One Flow Per Object