Crash? The software, or physically? A 200Hz as a min control loop rate seems on the fast side as a general default, but it all depends on the control environment - and I may be biased as I've done a lot more bare silicon controls than ROS.
Physically crash. When we would block the control loop at all (even down to 100hz), we would get errors and then occasionally the arm would erratically experience massive acceleration spikes and crash into its nearby surroundings before e-stopping.
Re: Other comment. Yes, this was with ur3e s which by default have update rates at around 500hz.
I'm guessing running a 200 Hz command rate on an e-series UR which uses 1 kHz internally will give you a protective stop?