Personally I think it also makes for a very nice desktop system. But I like my desktops thin, a tiling window manager and lots of terminals. If you enjoy fat desktops, there may be a bit more friction. One reason I like it for desktop use more than other systems is that the software packaging feel higher quality. It is not a huge difference. mainly I have found obsd packages to more reliably work when installed. and those heroic obsd package maintainers tend to put a note in /usr/local/share/doc/pkg-readmes/ that will get you started.
The documentation in all aspects is superb, and you can run all sorts of servers just fine (ports is full of common software). You can technically use it as a desktop workstation too, but I can't point to anything that really stands out in this aspect — except perhaps the strong focus on security.
But the simplicity also yields stability. Upgrading Arch for example can sometimes backfire. Upgrading OpenBSD? Almost blindly. It just works (tm).
It's very small and has a single button on the end for pairing, something like the creative bt-w3 [1]. You want to avoid something that won't work without windows drivers.
The os sees it as a separate audio device, doesn't care that it is bluetooth, and can be set to switch audio playback between the internal sound and the dongle automagically.
But I still have a creative bt-w2 audio dongle, and was curious, so I gave it a try, using mvp to watch a yt-dlp mp4, showing someone talking on camera. The bluetooth speaker was 3 meters away from my laptop. No tweaks.
It looked good, I was pleasantly surprised. It definitely had better sync than I've seen on some badly compressed cable tv content.
I wasn't familiar with how bluetooth buffering used to be, but I can believe it's caused problems. I've noticed sometimes when people are using bluetooth on their phones.
If the driver source is not freely available and it can't be reverse-engineered (or no developer is interested in working on it) then it probably isn't supported.