Also, the empty trains moving counterflow don't move particularly smartly at present --- there are only a few passing sidings and they have to stop and wait a fair bit to let the revenue trains past. I think GO sometime lashes two empty trains together to try and reduce the amount of track slotting needed.
To elaborate on the above. There are several sidings on the line, yet they are located in somewhat awkward locations that prohibit efficient counterpeak train movements.
One siding is near Bayview roughly between Gerrard and Danforth. Another one is north of York Mills. The third one is north of Steeles (south of the Doncaster diamond). The line is double-tracked north of Doncaster, but the second track cannot be used for revenue trains since this track has no platform at Langstaff.
From my observations, the "normal" evening schedule looks like this: the 4:30 (all times here by their original Union departures) train deadheads back and meets the 5:00 train at Steeles. Apparently, it can't make it further without jeopardizing that revenue train's schedule. It then meets the 5:30 train at York Mills. The deadheading 5:00 train meets 5:30 at Steeles. This last meeting is very often delayed for reasons I don't know: maybe the deadheading 5:00 is waiting for a crossing freight at Doncaster, maybe there's something else, like delayed departure from RH. Sometimes they eliminate the wait by keeping the 5:00 on the second track north of Doncaster. I don't know where does the deadheading 5:30 meet the revenue 6:45, it must be either Bayview or York Mills.
So for example 4:30 train has to wait for two revenue trains on its way back. IIRC, 3-4 years ago it somehow managed to make it to Bayview siding to meet the revenue 5:30, correct me if I'm wrong.
Anyways, if we consider it to become revenue, it would depart from RH southbound at, say, 5:20, then it would meet the 5:30 northbound at York Mills at appx. 5:52. It is then going to arrive at Union no earlier than 6:15, which is already 10 minutes longer than regular (and not very fast) RH train schedule. Add to that the usual delays at Doncaster, and this counterpeak train schedule is risking to become prohibitively long.
Yet the 5:00 train has only one other train to meet on its way back (the 5:30), so the standard delay would not be so significant. On the other hand, these trains normally rush past Langstaff at full speed on their way back, and still they're often late to meet the next one at Steeles, so making them stop at Langstaff will only make this problem worse, risking more delays to northbound trips.
Maybe they shall ask the people in their next Let GO Know if they would rather have ANY counter-peak service, albeit the one with such slowed-down schedule, or none at all. I would personally vote for such slow-but-existing one, but that's just me. How many other people would like to use such slower trains I can't estimate. Well, I'd love to have at least some counter-peak buses!
Richmond Hill has an end-of-line layover in the works to eliminate those empty train moves.
Instead of turning these trains into revenue, they're eliminating them. Bravo. While right now it's theoretically possible, though not very likely, to create the customer campaign in order to convert those into revenue service (which will no longer cost GO any more in trackage rights paid to CN since they own Bala sub now), with the introduction of the new layover the possibility of counter-peak service on RH line diminishes to below zero. I wonder if this extension to Stouffville Road and elimination of deadheaded trains will bring ANY schedule improvement (like at least a late-morning shoulder train or another train between 5:30 and 6:45 - a whopping 1:15 gap!), something is telling me that it's not likely: GO doesn't consider a train successful unless it's overcrowded. And they know that introducing, say, a late-morning train will not bring that many new customers, since the line is restricted by parking rather than anything else. But counterpeak service (especially evening) actually makes sense since parking IS available at that time.