fpath is not a replacement for a ls like command, but to change its output (I am an eza user myself). fpath takes output of eza to transform it into whatever I want. And its not just usable with an list program such ls or eza, but also operates on stdin like grep, even non existent files to maybe form something on a different place with same name in example. I still use ls (which is eza for me as an alias) for regular day operation.

fpath is useful for output from find command or baloosearch6 (KDE's file indexer, that only outputs full path of matching search). In this case eza does not help me. Sometimes it can get messy with using sed and grep mulitple times and Bash substitution to get file extension and so on. Or I use baloosearch6 "Super Mario World" | fpath -F{name} -x*.pcm to just show filename, excluding all paths matching *.pcm glob (not regex) for whatever reason I want to use. The thing is, this is just a moment to be in. Next moment I can easily adjust the output to output it with or without other information.

Aliases to common commands so it gets automatically formatted.

It's a bit hard to show examples that justifies such a tool. But it's not about making things possible, as there are other tools like ls, grep and sed and awk and Bash commands to do all the formatting and output. But its a little bit easier and more flexible to have fpath, which understands paths and has dedicated functionality to support that. It's more about being flexible and doing it in place easily. At least for me, because I know the tool.

Let's say I want to output some information about files that come as a result from my file indexer baloosearch6 (from KDE). It only outputs full paths. Let's say I want to show only its names and the file type information (or any other) next to it:

baloosearch6 "Super Mario" | grep /snes/ | fpath -F'{name}\n\t{file}\n'