MISSION ACCOMPLISHED, here's how I did it:
I installed a VM of the latest windows 10 ISO and located the driver file for the xbone controller, then saved a copy of that to my host OS. I took ownership of the xinputhid.sys driver file (I'll detail this in instructions below) and replaced the newer 10586.122 driver with the 10586.0 version. Doing this causes windows to still think it is using the 10586.122 driver, so it should not be overwritten until another update (newer than .122) comes out at some point, but for now the controller works normally for both xpadder and the games that I tested (unlike the generic driver that I also tested). This fix should still be considered temporary, as there may be some issues which I did not encounter, or a future update may overwrite this fix. I take no responsibility for any problems that occur from this fix (If you do have any issues, you can feel free to report them in this thread and I will reply when I can!), and you should follow the instructions below AT YOUR OWN RISK.
INSTRUCTIONS:
So first off, you CANNOT have your controller plugged in or connected wirelessly, and you must be logged in as an admin on your PC.
1. Locate the driver file (xinputhid.sys) under C:/Windows/System32/Drivers
2. Right click the file, select "Properties", then go to the "Security" tab
3. Click "Advanced", then select "Change" on the Owner line, and type in the user name of the primary account on your PC (if you use a Microsoft account, this will be your email)
4. After typing in your user name, click on "Check names", then press OK to close out of the Owner and Advanced properties windows
5. Close out of the Properties window and reopen it, go back to the Security tab and give the "Users" group full control of the file
6. Rename the file to xinputhid.sys.old, or move it to a backup folder
7. Download
this file and place it in the location of the original