These impossibly idiotic scenarios described above have been a feature of simulator "training" for decades. Management pilots who dream up this nonsense get bored with routine simulator sequences and we all know that the Devil makes work for idle hands. We had similar nonsense at Central Flying School where as part of an instrument rating test in a Dakota, one had to perform a single pilot, asymmetric, limited panel (no AH or DG) NDB aurul null instrument let down.
The recent dreadful accident in Indonesia where a 737-200 of Mandala Airlines appears to have done an airborne abort seconds after lift-off (gleaned from notoriously unreliable media reports), is one accident where simulation of the events could be demonstrated in a simulator to show the potential for disaster caused by a late decision to abandon a take off. It looks like the Mandala 737 may have suffered an event very late in the take off run that for some reason caused the captain to abandon the take off- - with disastrous results.
Rather than invent complicated and highly unlikely non-normal scenarios such as those described in this thread, there would be better value if crews were given an event at V1 or VR or even V2 that has previously happened in real life and which has caused a reflex abort action which proved quite dangerous
For example, a door warning light coming on, or a generator failure light, or a reverser actuation - things like that which require fast and correct action.