Actions like 10j don't instantly move 10 lines below

Is your feature request related to a problem? Please describe.
Counted motions like 10j are not instantaneous. Instead of jumping directly, the editor scrolls one line at a time. In large projects or when the CPU is under load, this becomes noticeably slow, especially for larger motions like 50j or 50k.

Another issue is accidental input of extra digits (for example, typing 500j instead of 50j). This triggers a very long animated scroll, and there is no easy way to cancel it other than restarting the editor.

Describe the solution you'd like
Add a boolean setting that makes counted motions jump directly to the target line instead of scrolling line by line. The editor should calculate the destination first and move the cursor instantly.

Describe alternatives you've considered

vscode-neovim does not have this issue, but it is too unstable for my work environment.
Using gj/gk is not suitable because those motions operate on display lines rather than actual file lines. Since I use word wrap, I specifically need movement by file lines.

Additional context
This issue becomes much more noticeable in large files or when the system is under heavy load.

No implementation file or test is named. Start by locating the counted-motion handling for commands such as 10j and 50k, then find how existing boolean settings are registered; done means a setting can make these motions jump directly to the target file line without changing gj/gk behavior or word-wrap semantics.