What problem do you see this solving? Capture One starts by default with the most recent session opened - this might be problematic as it changes timestamps on its .cosessiondb file and would be an unnecessary use of resources, if not planning any...