Fwiw it's not very useful to rebase every day. You don't need to update a MR unless there's actual changes to be made, and when you do it's also better to avoid rebasing unless there's conflicts, so that Gitlab diff can be used to compare the changes (otherwise it's pretty much unusable).
If you want to get some feedback it'll be more effective to look for someone (ask here or in IRC, or figure who could be knowledgeable) who's happy to review your changes, and assign them as reviewer.
Regarding this MR specifically, the issue might be that nobody's knowledgeable enough about WLAN APIs to give relevant feedback.
Then a general feedback I can give already, is that bridging DLLs directly to the unix side is the easiest way, but not always the right way to do things. It's unclear to me (because I know nothing about these APIs) how the handles/objects returned by the APIs here can be used on Windows, and whether we're going to get stuck in a dead end or not if we go that way.
For instance, are these handles related in any way to some underlying devices or are they truly wlanapi private handles? "Should/can/what about" we expose the WLAN devices as NT devices instead?