Hello,
I have downloaded your driver. It looks fine. In fact there is no driver at all in the package, just a surrogate, mambo-jumbo to let it look Google inc.
Nonetheless I installed it on my game box (I don't care much as it is not my development box).
Installation of the driver had immediate effect on how it looks in Device Manager
Nonetheless, adb devices or adb shell worked perfectly with Boox Max
I decided to try the uninstallation path. So I clicked in the Device Manager on the device, then have chosen "Uninstall driver"
After reboot, the device in DM looks like before
adb devices and adb shell works as usual.
You mentioned the 'lemobile' driver. I have no idea what is it. Maybe it does some mischievous maybe not. If you manage to get the DM display Max as your device, using MS drivers, then I would say it has nothing to do with any other drivers you installed on your journey.
Last thought, are you really sure you enabled debugging on the Max? Otherwise I would recommend to go to anyone around you with a computer and try adb. You can just copy the google platform tools on a usb stick and try: windows 10 does the driver magic out of the box as you see now. Linux and Mac users also do not care about any driver, though the adb comes from different package.
EDIT:
You know you can also install ubuntu on a USB pendrive, just boot from such pendrive and try adb in Linux environment.
EDIT 2:
Now I am laughing I have not asked about that at the beginning: What usb cable are you using? Are you sure it is full micro-usb cable. I have such fancy cable which came with Beats headphones which looks just normal but does not work for android development as it is meant only for charging. Make sure you are using full micro-usb cable.