Emulator

Don't we already have ten of this same feature request lying around? I'd probably hear about it every day if I still bothered with the forums.

I don't see the issue with this as long as it isn't default functionality.

I'm not sure why you would call it "velocity input", as it doesn't seem very intuitive for newcomers and may cause some confusion with some controllers' gyroscope function. I know it's technically correct as the joystick is controlling the displacement rather than absolute location, but there must be some better term for it.
In my experience, I've had some problems even with Metroid Prime 3 as you either had to completely center the target for it to lock on, or hold the stick in a certain position. This can get quite a bit frustrating when having to push 2-3 buttons while doing it. What prompted me to make a request, however, is the pull stars from Super Mario Galaxy/2, which turned from a benign and mindless experience to just tedious work.

Is there any way to implement the same solution for tilting and skewing? I think it would be helpful for games like Skyward Sword and Metroid: Other M.

What would be really impressive is if you could map the mouse pointer 1:1 with the Wii pointer.

Each game does different things with Wiimote IR... so... no?

I mean, I'm sure anything is possible with emulated Wiimotes, but 1:1 probably won't happen because the position of the Wiimote displayed on screen depends on the game/software. That's the only reason it currently isn't 1:1 anyway.

What would be really impressive is if you could map the mouse pointer 1:1 with the Wii pointer.

That's completely unrelated to this feature request, and not really possible as each game describes it's own mapping between IR and the pointer location on the screen.

I think this is good time as any to ask for updates about this suggestion. I mainly worry it'll not make 5.0 as many users don't use the dev builds, and its release date is currently TBD.

Seeing as it's past feature-creep deadline and no work has been done on it, is there any chance it will make it into 5.0?

We are in the feature freeze now, and would be a new feature, so it by definition cannot be added to 5.0.

I think this is a duplicate of this old feature request (#3033).

PR 4010 makes an attempt at implementing this.