Even if it were fuzzy (which can be tested piping Powershell's 'Get-ChildItem hklm:\' into fzf for instance), you'd need a lot of filtering to make that useful though (I'm guessing you don't want to see recent files whichhappen to contain the name of the thing you're looking for) and/or search specific trees only and/or limit depth. But even that won't immediately solve the usage of cryptic names.

Better starting point would be Group Policy, which is mostly a layer over the registry but containing pretty good descriptions of what a setting does. It has a Powershell module, so combining that with fzf and a preview pane which shows the description might ctually be pretty neat, but probably not very fast.

no I'm not, regedit is another usability nighmare which doesn't fulfill any of the conditions I've described, and search is not only not fuzzy, but also slow (Everything can search through the whole filesystem in less than a second, Regedit takes it sweet time)

And it also lacks any visual cues, so if you're used to some icon in the main settings apps, you'll not see it in regedit

The whole point of what they were asking for was for the thing to be highly usable. Regedit is... not that.