I agree. Provided that it’s not a pain to implement and that it cannot be abused by third-party apps, read-only capability beyond $home would be harmless, but very useful for system exploration and understanding.
May even help with basic diagnostics for those who are afraid to get into devel mode/terminal (and it’s safer than throwing commands without understanding)
But if that’s problematic, I think it would be better to just grant the store version read/write capability for all of $home sooner (maybe with a warning about hidden folders like .config or .local), and deal with anything beyond that afterwards
Tangential edit: However, I want to add that File Browser is very useful for quickly editing big text files, as both Editor. and Seabass seem to struggle with files over a few thousand lines. But for the Store version, limiting that ability to $home makes sense