Yeah, I'm really wondering why they thought this was a good idea. My best guess is that they want to keep everything within one file, since it makes the script easier to deal with. But when automation actually starts being implemented, they want the functions for each task to be grouped (and I believe, Python doesn't support inline modules), so they ~~ab~~use classes for that...?
Well, and I guess, it allows them to have pseudo-constants within each task, which don't need to be explicitly passed around between functions.

But yeah, really not a fan of needing this much boilerplate to start out with. In my opinion, the activation energy required to use this pattern instead of slapping down documentation needs to be as minimal as possible, otherwise folks will slap down documentation instead.