I agree whole heatedly with you about the quality of a obsd router/fw. I don't support enterprise networks so my viewpoint is a little different. Unlike ios and cisco hardware current OpenBSD releases are finicky with commodity hardware. I remember being able to pick any old box (486, ancient pizza box sparcstations) and being able to set up a OpenBSD firewall on it pre/post ipf debacle. Recently I have ran into a number of boxes that I could not get openbsd to boot on, most recently two older shuttle boxes. Hardware support is what really troubles me.

On a completely unrelated note I think too many people overlook the contributions of the OpenBSD development team when it comes to Openssh. On a much lesser scale they have also given a lot to the OSS community with OpenNTP. For clock synchronization you have the ntp reference implementation, openntp and Miroslav's chrony. For desktop machines the reference implementation leaves a lot to be desired (especially when it comes to power saving) and or is massive overkill for the problem at hand. Unfortunately chrony seems to be the only clock synch tool that is mindful of power saving and suspend/hibernation. OpenNTP synchs clocks with acceptable accuracy for common use cases without running a ton of code that only a few people fully understand.