No it isn't; the hive metaphor entirely fits the Windows Registry, which is a kind of hornet's nest where configuration goes to disappear.
The person who came up with that was developing it seriously, and the naming almost certainly had to have "buy in" from other "stakeholders" in the project.
seems like you didn't read the actual article. it's short enough to include here.
"""
Because one of the original developers of Windows NT hated bees. So the developer who was responsible for the registry snuck in as many bee references as he could. A registry file is called a “hive”, and registry data are stored in “cells”, which is what honeycombs are made of.
"""
I read it several hours before writing that comment.
Regardless of the motivation for the naming having come from tormenting bee-hating guy, the naming had to make sense. The developer in question would probably not have gotten away trying to call a registry root "fiddlestick". He had a boss, and peers, and they signed off on "hive".
Perhaps that person had some creative name for the entire thing instead of "The Registry" (Apiary? Ha!), which perhaps had been overruled. The "Hive" jargon is not really end-user-facing, though.
The person who came up with that was developing it seriously, and the naming almost certainly had to have "buy in" from other "stakeholders" in the project.