Smbus controllers(?) rationalization

So.. Not sure if this shouldn't relate to #3916, but anyway while banging my head against #631 I noticed on librehardware that on linux (where real drivers for Super I/O kind of exists) they do rely on OS functions. Shouldn't you also do the same? Or are the functions all too specific to hwmon?

Slightly related to that (and given the sort of issues we were having), is it actually necessary for all the different controllers drivers inside of OpenRGB to handle themselves the access to chips and rollout their own ControllerDetect? Like.. Of course AORUS and Mystic are going to need different commands sent, but could a common LPC/EC interface abstraction be helpful?