Here are my 2 cents on this:
Philosophically, all moderators generally shouldn't unilaterally close a question with a single vote if we are not 100% sure (or maybe 88% sure) that it's off-topic or the question already has issues with confusion, divisiveness, or is actively harming the site.
I try not to assume something is unsaveable, unanswerable or off topic when I'm in the review queue or not reacting to a specific flag.
Now, if 4 site members had voted to close a question the presumption of it being truly off-topic is more likely and I would want to be able to make an edit or point out a clear flaw in the close reason before unilaterally re-opening it.
Now - as for this question in specific. Yes, there is clear mention in the setup that a developer happens to be the user, but in the specifics no code (Objective C, Xcode compiling or API) are actually involved in the topic. It is pure terminal commands that are accessible to each and every Mac that ships. You don't need to be a developer to answer the question, you don't need to install Xcode, you don't need anything except for knowing that terminal exists and that Apple's OS exposes hardware details to shell scripters and that the GNU tool
nm lets you map the details of a file.
So, if we are to allow questions about "homebrew", "gcc", and other open source tools that rely only on the terminal - it seems odd to throw out this question that uses open source tools to look at Apple's hardware. Similarly, you can use command line tools to check GateKeeper status, code signing status, whether the network connection is wireless, ethernet or something else and I see this question as fundamentally about how someone can know what hardware is installed by using OS X to get at hardware details.
I happened to know all this, so I was able to flag this question for re-opening, but I wanted a meta thread to explain the difference between closing something that we knew as asked was off-topic versus something that might get edited or answered in an off-topic manner.
Despite all that, this question doesn't have enough details to make it "system-admin friendly" in that the specific problem isn't with loading or unloading a
kext but with finding an API that's declared in the kernel (totally fine for this site) and looking for the development portal to access that undocumented internal API. (totally not fine for here)
I'll close this again which is what the first moderator did unless it gets edited to be more on-topic for admins as opposed to developers.