The problem with this request is that LOGseq does not have such a strict distinction between navigation mode and editing mode as VIM.
We have also discussed this here:
LOGseq is currently following the path of making it easy for the user to write text and, as far as possible, providing the behaviour of a “normal” editor. This means that keyboard shortcuts with individual letters are not available for navigation between words (in navigation mode you are navigating in block units not characters or words).
This is a fundamental decision of the developers which concept LOGseq follows.
The original requirements of @IcedAndCorrected are possible because the shortcuts only refer to the navigation mode and function at block level.