NWN for example is keyboard and mouse. Very very easy. You need an API to ask the mouse position, and one to ask the mouse state (Clicked or not and which button).
Most games don't even bother with checking the capabilities of your mouse or keyboard. So DXInput is not useful. Where it becomes useful would be games like console conversions... which is the majority of PC games these days. I noticed long time ago that with XP, it doesn't seem to be required. I have never fully tried it myself, but I am guessing XP simply reports that you have a joy stick and/or throtal/yaw control. And how many buttons you have.
I am unsure how things like rumble work, probably using directX or something else.
I did code briefly in VB6, a walking sprite that could be controlled by the joystick on my gamepad. Getting it to move was easy, just API calls to check its status, though the enumeration... was confusing, had to use copy&paste tutorials. Getting it to be analog... sort of had me stumped. I could only get it to send a short signal. This when it happened, my code would error out with an overflow from the API, resulting in a send error report kind of error.
Keyboard movement, was a simple, barely 20 lines of code.
Using a mouse as a camera is really easy. Move the mouse to the centre of the screen every frame, and just before doing so, grab the current position of the mouse, and subtract it from the centre position. The "difference" is how much to turn a camera, the "difference" in size from the previous "difference" is the acceleration.