Controller on Bluetooth mode breaks after using the library

[AryanRarestand]

Before loading the library the controller works just fine but after loading the library the controller is still being recognized by windows but no input is recognized.
Now I did a little more digging and I found out the input report is changed after sending the first output report (this only happens when we're doing it through 0x31 report id which is the bluetooth output report id) and thus windows cannot recognize the newly structed input report and the inputs will be ignored. This ONLY happens through Bluetooth and doing it through USB works just fine. I've seen other apps using an emulated controller driver as a workaround but I wanna see if there's any way to prevent this from ever happening.