I made no statements that the train would be locally self engineering using the cameras.
* the last junction you passed and how you exited, and
* number of turns of the wheel.
The issue is that rewiring junctions is very expensive, upgrading trains to be compatible is expensive, etc. Even more so if you cannot upgrade an entire network all at once, and you need to account for mixed operations with both new and legacy compatible systems.
The pressure to reduce crew costs means longer trains and less network fluidity; automating them allows much shorter point-to-point consists on the same infrastructure. As long as they have the right sensors they can run much closer together - even couple & de-couple en route (with some extra equipment).
The issue with networks is that it is impossible to roll out automation all at once, and the intermediate mixed automated/non-automated network is more complex and harder to do safely and reliably.
NYC has been moving to (theoretically automatable) CBTC signaling from mechanical signals. It's been challenging.
* The CBTC and mechanical interface has issues and constantly fails over the entire system
* The mechanical system is itself falling apart because it dates from the '30s, and is so old that the suppliers no longer exist and they source parts either from collectors on eBay or make it themselves, and this is also affecting the first bullet point
* Few modern suppliers of signaling actually sell fixed-block signaling that can handle the capacity required today, and even if they did, would it make sense to spend hundreds of millions or billions on a stopgap to CBTC, which will also cost hundreds of millions or billions?
Rail utilization will certainly help at the margins, but only maybe one or two trains an hour. The real meat and potatoes is generally more tracks, and removing conflict points on existing ones.