I completely disagree with your assessment of the two choices. Releasing an immediate security update independent of 10.9.2 was the only reasonable course of action. Holding off on a significant patch for days just because it doesn't suit your release schedule for unrelated stuff is ridiculous.
So, it turns out that they had a point release very far down the release engineering pipeline that included several new features (FaceTime Audio, FT call waiting, Mail bugfixes, et c).
A few days ago when the TLS bug became widely known they had two options: push a point release for _just that_ near-immediately, followed by the existing planned release (after redoing QA because the TLS changes would require the feature-add release be rechecked), or just integrate the TLS fix and restart QA on the planned release. They opted for making everyone wait a few days and just doing one release.
It was a trade-off, and both would have been okay decisions IMHO. There is a non-zero downside to releasing OS updates too frequently with an installed base as large as OSX.
"Unconscionable" it would have been if it had dragged on for a week or more. This was probably a heroic effort by the release engineering team(s) to get it out in in the timeframe that they did (after opting for just one release).