This is probably not helpful to you years later, but for the benefit of others:

Not all software uses the Registry in a responsible manner. This does not automatically imply corruption, but it does imply bloat. The Registry really isn’t designed to be used to support tens of thousands of data entries for a particular piece of software. A better implementation would be to have a single entry that points to a private file that stores this information. It can and is used in this manner, but it shouldn’t be: it’s sloppy programing.

Registry corruption tends to happen when data in the Registry that references other parts of the Registry gets broken. For example, a class is defined, but other data supporting that class is removed. This is logical corruption. Physical damage to hive files can also corrupt data, but neither is usually catastrophic.

Most every Windows installation will have some degree of logical Registry corruption, but most of the time it goes unnoticed. The Registry is really closer to a simple file system, than a database as some people try to describe it. The same ills that can happen to file systems can happen to the Registry, too.

It’s been around a long time.
A common problem I’ve seen is that environment variables stop expanding if the Path string is saved as a REG_SZ type versus the REG_EXPAND_SZ type it’s supposed to be.

I’m checking for potential compatibility issues with referencing other environment variables within the %PATH% variable itself. Been searching high and low for this, but I have yet to find a definitive answer.

If you think it Is a “a sloppy piece of software” and are not comfortable using it, then it better to uninstall it. At least I would uninstall any software right away if I did not find any value in using it.
CCleaner or for that matter any registry cleaner, will help in removing broken or orphaned registry entries only, and not fix a corrupted Registry.