Hmm, I figured as much for Scantime and Expiry. I've always left queue to the default of 1, no matter where I've been. I can try it again later after the updates.
Queue is actually "extra work items in queue", that's why when using 0, staged work (ST) is still at 1. It was useful back in the days before stratum, but since now work is locally generated (LW) at will by cgminer, it only serves as a hindrance on coin switches, although it shouldn't be happening.
Terk, are you sending "Clean Jobs == true" on the stratum work packet? (params[8] == true)
Clean jobs is set to true when the pool sends new work because of new network block found. If only merkle root hash was updated, then clean jobs is false. Also, it is always set to true when sending first work for a new coin job after coin change.