Oh god, Confluence. I'm so sorry man.
I don't have much to compare it to. Pre-Confluence, Line 6 was using TWiki markup language and at one point I was literally the only person in the building who knew how to write in TWiki. It was hell, but my previous gig emailed offline Word files, so...
Other than it not being designed for massive, single-page documentation (too many tables slow it down to a SLOG) and a few formatting quirks and bugs, I can't say too many bad things about it. We use Jira for stories and bugs as well; WAY better than Scrumworks and Bugzilla.
Don't get me started on Omnify. Other than a recent graphic assets refresh when they switched their name to Empower, I don't think the layout's been updated since the 90s.
it turns the amp into a Line6 original. That's how I see it in theory.
It's a lot more subtle than that, but sure. In beta, no one's really agreed on the best setting per amp, which to my mind isn't a bad thing. Person 1 loves Amp A with Hype at 7.0, Person 2 insists it's best at 3.0, Person 3 insists on leaving it off. Then for Amp B, Person 1 likes Hype at 1.5, Person 2 leaves it off, and Person 3 likes 5.0.
"Idealized" isn't the best verbiage, but there's too much nuance required to explain exactly what Hype tries to accomplish, so at a certain point you just don't push back too hard on the 25-word copy. Here's what appears when you tap the parameter:
"Depending on the amp and settings, increasing Hype may subtly or dramatically adjust various behind-the-scenes parameters to make the amp sound and feel smoother, fuller, punchier, tighter, and/or more forgiving, but at the expense of accuracy."