Conclusion was that yes, you can predict locations of the terminals, but it's quite hard to find and produce repetitive schedules from the data because it requires the ships not change their schedule for too long, and the reality is just too dynamic to properly predict this.
For seagoing vessels I expect that they have more predictable schedules, but the hard part there is knowing container volumes, because there is no way to predict from public data what the volume of containers loaded/discharged is at a specific terminal. The closest metric is measuring the turnaround time of the ship, but that is not a great predictor for number of containers moved because handling times per container will differ per port, as will the number of cranes assigned to the ship, as will the ratio between 20ft and 40ft boxes, as well as the capability per port to do twinning (picking up 2x20ft boxes in one handling) and dual-cycling (discharging and loading a container as part of the same crane cycle).
Basically: it's a tough problem, with too many variables you cannot reasonably deduce.
(Also, even if you have the container volumes, I personally think the highest potential for optimization is in the hinterland, but that's a different story altogether)