Report #1: A minor, but potentially hazardous (confusing), GUI issue
I may have reported this once before for an earlier release. The "Render Engine:" option in the Configuration dialog triggers screen updates when the MOUSEUP event is received (for adjusting to DirectX or OpenGL mode appropriately). This trigger doesn't work when the Render Engine choice is changed by a key press or, a method I sometimes use, with the mouse wheel. Possibly a better event to look out for is CBN_SELCHANGE.
Report #2: Some info on the "Force Nearest Filter" issue...
It doesn't seem to matter which of the three options under "Force Texture Filter:" I choose. They all seem to do exactly the same thing (literally) --as if that option didn't matter at all. The plugin seems to choose Linear or Nearest at some inconsistent random: In one scene, a piece of graphics will be Linearly filtered (in no apparent consistency to how other graphics in the scene are filtered).. but in the next, a similar graphics can be Nearest filtered. The choice of filtering used at once specific spot in a game seems to be consistent accross emulations however.