LinuxQuestions.org - slow fish dir/file completion

no matter which distro i use (and i've used hundreds), i'm mostly using a janky system most of the time (mild exaggeration), typically presumed likely due to pebkac (probably wise to lean to that thought first). ever unsure if it's me or where in the machine (so, i plan on remembering to suggest bedrock only to users who seem more competent than me H_H). foremost example on my mind:

my fish shell, often when doing completion (often/mostly/always?) over an sshfs mount, it often takes many many long painful seconds to propose the next location, hanging unresponsive while doing so. there are several /old/ fish issue reports of slow sshfs completion (and other current open issues in their tracker for "slow" and "completion" that dont mention sshfs in the titles), and i dont recall fish completions over sshfs on plain devuan ever being slow. so... bedrock? something spinning through endless cascades through etcfs or something?

that's my best guess so far for why sometimes completion of next dir/file hangs in fish. something's sending it off looking the long long way around all possible ways around before actually just completing, as it should, instantly, if not being held up somehow.

not sure what where how at that stage... what to check for next...

this, on:
fish 3.0.2 (from void, my hijacked and init stratum).
Bedrock Linux 0.7.6 Poki (though i've not rebooted, not sure if that means it's still 0.7.3(? or .4? or idk).
with
SSHFS version 2.8
FUSE library version: 2.9.7
fusermount version: 2.9.7
using FUSE kernel interface version 7.19
Linux 4.19.34_1

any pointers where i should look next to diagnose/remedy the problem of these long completion delays?

could my use of an extended version of https://someonewhocares.org/hosts/ be at play here? ~ if so, how would one, without having to give up a someone who cares hosts file, remedy the delay?

*posting this to let my headspin settle*