Moksha's screen blanking does not support any integration of any sort - it is fairly minimal.
I just toggle presentation mode on / off when I want and don't want it.
I suppose you could edit your kodi launcher to automatically turn presentation mode via the enlightenment_remote command when launching kodi, but I don't have a good thought off hand on turning it back on automatically when kodi is stopped.

You do not need a PAE enabled kernel if your system has 4 gigs of RAM or less. PAE just allows your computer to use more than 4 gigs of RAM on a 32bit operating system.
After installing the Legacy version you can install all of the applications the app pack build comes with via the command:
sudo apt-get install bodhi-apppack

First off - welcome to the forums.
As for your issue - it sounds like suspend / resume just doesn't support the hardware you have. In addition to removing the suspend on lid close from the ACPI bindings, you also need to dig into the systemd settings which trigger this as well. To do this you'll want to edit the following file with root permissions as such:
sudo epad /etc/systemd/logind.conf
And then comment out / toggle off the suspend on lid close settings.

If you check the list of build deps on the GitHub page for Ubuntu 16.04 these should roughly translate to similar package names for Debian: https://github.com/JeffHoogland/moksha
I personally do not have any plans at this time to build packages for Debian. The only time anything officialish from Bodhi has been built directly on Debian was when we had an ARM branch that was far too much work.

I don't have any experience with ndiswrapper personally, but just wanted to chime in that in general Bodhi is backward compatible with directions for the Ubuntu base it is built on. So this means if you are using Bodhi 3 any directions related to Ubuntu 14.04 on this matter should apply for you.

Can you post a screenshot of what you are seeing? What is the file path your file browser is trying to open to? I'd guess a bad path is being passed.
Assuming your wine prefix is the default, what happens if you navigate to: ~/.wine/drive_c