Editing, sure, you've got essentially a single GUI application and CLI or programmatic access. Your options are certainly more limited than the plethora of text editors available.
You can export a registry path as a text file, make changes in perferred editor, then import it again. It's annoying but I've done it before when needed.
PS> cd HKLM:\Software\Microsoft\Windows\CurrentVersion
PS> ls
[...bunch of stuff...]
PS> gp Themes DesktopBackground
DesktopBackground : c:\windows\web\wallpaper\[...default system wallpaper...]Pwsh is pretty neat in that regard. Besides the actual filesystems drives, many systems have "providers" that allow you to treat their objects as files: the registry, environment variables, the functions defined in your session, the variables, the aliases... Unix's "everything is a file" became "everything is an item".
* a uncorrupted registry hive is supposed to be Directed Acyclic Graph, (while a modern filesystem can have arbitrary cycles with symlinks and bind mounts and junctions) and;
* the registry has more limited name length limits, even assuming Windows somewhat low filesystem name length limits.
Or, from the contrary perspective: it’s the 500 places config lives on Linux, but in one place instead.
(Except it still has a deep hierarchical structure, so that second one is kiiiinda not entirely true, in that you can run into exactly the same issues as scattered config files on Linux)