If the node is created with a delay=x value then chutney forks a child, sleeps for x seconds and then execs tor. This likely can be improved. Branch bug10155 in my repo.
It looks like we've diverged a little; fad78679d34e4f345b13942e9bbdc0ddbbb52e13 is the commit I should be reviewing here.
I like the idea for the feature, but I think this argues strongly for some kind of scheduler/driver-based thing, rather than a bunch of fork/sleep/exit backends.
Then again, nobody's written the scheduler/driver thing, and this would work today, I bet.
What tests have you done with this?
How well does this work if you say "chutney status" or "chutney stop" before the delayed tor nodes have started?