Ckan is the one I tried to use, but the resulting KSP1 installation usually threw a ton of exceptions at runtime. Maybe it's just compatibility issues -- those weren't called out, though.
The jank was also forgivable when it was a one man effort or a very small team. Plus it was a relatively novel idea for the game being created for the first time. It also made no grandeur promises of what was to come, and continually made improvements.
Take Two and KSP2 have none of the same forgivable qualities.
The jank was acceptable because it was supposed to be a simple 2D game that ended up outgrowing it's diapers as it grew, and being a Unity project a long time ago, was stuck on abysmal physics systems. It couldn't NOT be jank. Everyone always "wanted" a better physics system or game engine entirely, because KSP1 was often held back by Unity, but that would have definitely killed the project.
Then KSP2 is like, still on Unity? Despite massive amounts of budget and like no compelling reason to stay on Unity with the backing of a real game company.
I wouldn't go that far. Its not KSP2, but KSP1 has plenty of jank and bugs.