Utah,
I don't have first hand experience with the S9 or S10 IRD's, so I am a bit lame here.
However, I have questioned this in the past with my AZBox's. With the AZBox, it wakes up (if in sleep mode) and prepares for the timer recording function to begin ahead of time. So, it actually seems to drive the motor to the satellite where the channel to be recorded is before it starts the record timer. It seems to do this even when parked at a far off sat, almost as if it knows when to set it's own alarm clock earlier so that it is at the channel to be recorded in advance, and then it begins recording right on cue.
That seems a bit far fetched to imagine that it is that good. So, what I think is going on is that the AZBox has a built in PREP timer that is longer than 1 minute. One minute is longer than the time required for my motor to travel from one end of the horizon to the other (30.0°W to 125.0°W or vice versa) which gives it plenty of time to start the recording event.
Now, we are examining your S10's record operation. What I would like you to clarify for me is this. Does the RECORD event cancel itself because it doesn't detect a valid signal in time, (because the motor is still travelling)?
If this is the case, then you will have to set two timers until they provide a firmware upgrade or option to correct this. But, if you have the option, I wouldn't schedule a RECORD event to move the dish, I would schedule a PLAY event. I have this option on my AZBox. I can schedule a RESERVED PLAY EVENT, so it moves the dish to a desired channel, but it doesn't record it. Then, the RESERVED RECORD EVENT can execute normally and on cue.
This doesn't really help you any because you are still in the same boat. It sounds to me as if they didn't program the firmware to accommodate this scenario. Unless someone else has a trick up their sleeve, I don't have much that I can offer other than to understand your dilemna and relate to it.
RADAR