honestly, you are best mapping your own keys. decide what you want the buttons to do and go in to the input gestures part of the settings and add them in.

Personally: ...
*I like 2 of the front buttons representing shift+tab and tab.
* I map dot 8 Or enter) plus the braille numbers to the function keys, so I can always press f5 to refresh or f7 to spellcheck or f6 to hop between window panes or f2 to rename, and so on and so forth.
*I map the rocker bars so the right one is up/down and the left one is left/right. I rarely need to use left/right for text editing because of the 40's display length, but left and right cursors collapse or expand views sometimes. Both rockers up is page up, and both down is page down. home is space and l, and end, space and dots 4-5-6.
* I map the control keys to their initialisms: space plus A, C, S, N and W are mapped to Alt, control, shift, windows and NVDA. I can then press these, then another letter, number or shortcut to press them with an appropriate set of modifiers.
* I then map a variety of useful shortcuts: space plus q for alt+f4 (q as in quit. Space+e for escape, space+dots34 (st) for start, space+t for alt+tab (although sometimes I remap to alt+escape). Space+s for speech on off, space+m for the context menu (shift+f10). enter plus p for power (battery status) and t for time, which came from the BrailleNote years ago, as did backspace plus dots2356 for delete, and g for say all.

Sorry, there must be more, but I am typing on mobile and can't quite think of them. I'm sure you get the idea by now! IF you can't find all the input mappings in the UI, you may need to go in and edit the gestures.INI file (you can do a windows+r for run and type %appdata%\nvda\gestures.ini for the installed copy's version). There is literally nothing you can't map with a bit of forethought. I regularly use a display for reading and driving my whole system, often several metres away from the actual computer not relying on speech.