As of latest master (2b770080a49f282e51b7e4d176b2d9fbe0f8f5db).
0src/bitcoind -testnet -stopatheight=100000
1
2...
3
42018-06-15T12:49:59Z UpdateTip: new best=000000000086a985696447c96c8a3520dbe5536287ef9fbf5b220b66fdb684c7 height=100208 version=0x00000002 log2_work=54.043471 tx=599130 date='2013-08-11T14:57:43Z' progress=0.032961 cache=43.5MiB(302489txo)
52018-06-15T12:49:59Z UpdateTip: new best=000000000060c93d2cf7a5cd5ce510c31cf96b983ee64ec5c627cf2055249500 height=100209 version=0x00000002 log2_work=54.043562 tx=599131 date='2013-08-11T15:01:20Z' progress=0.032961 cache=43.5MiB(302490txo)
62018-06-15T12:49:59Z Shutdown: In progress...
72018-06-15T12:49:59Z addcon thread exit
82018-06-15T12:49:59Z net thread exit
92018-06-15T12:49:59Z UpdateTip: new best=000000000075b13f384b05ac740b776593dc4f53d2d92cf9c2a81475335a3cef height=100210 version=0x00000002 log2_work=54.043653 tx=599136 date='2013-08-11T15:09:42Z' progress=0.032961 cache=43.5MiB(302495txo)
102018-06-15T12:49:59Z msghand thread exit
112018-06-15T12:50:01Z opencon thread exit
122018-06-15T12:50:01Z scheduler thread interrupt
132018-06-15T12:50:01Z Dumped mempool: 7e-06s to copy, 0.00237s to dump
142018-06-15T12:50:07Z Shutdown: done
Having precise control can be useful for generating a deterministic blockchain snapshot. That in turn could be useful when bootstrapping a low performance device (though hopefully #9483 will make that unnecessary), as well as for validating the chain in parallel on multiple machines.
One easy solution might be to just roll back to the target.