It's helpful unless you're running X-Term with the intent to do something else. But that's neither here nor there.

But do you know why it does this? I would love a technical explanation for what happens at the deeper software level that causes X-Term to crash after the second time running the commands? Do you think it was caused by running both switches in a row in one X-Term session? Or is it something that was initially caused by switching to the new keyboard, and the both-in-one-section thing had nothing to do with it?