this assumes that by accessing that driver you intend for the sound to take priority over anything else running on the system.
that may be true for you, but is it really true that it's _always_ more important to get a system beep than to write to the database file? I don't think so.
to some extent, the fact that you need priority is a system bug (when the system is not overloaded), and that should be fixed. but that won't be enough for people pushing their systems to the limit with audio processing (but I would argue that if you want to make the audio processing the most important thing on the box, you need to tell the kernel your priorities)
many times when you are running an high-end audio app you are also doing a bunch of number crunching (to compress the data, to display graphs of the data, to uncompress the data) how is the system supposed to know what parts of this you are willing to have slow down?