Ha. Ha. No.
To offer the opinion of a former 3DS CFW dev, Atmosphere is pretty freaking well coded. It's taking so long because they're not patching components of the OS, they're writing open source reimplementations with extra functionality to support the CFW use case.
If you find reading and understanding an unfamiliar codebase to be a nightmare, you should quit programming. People do this all the time - it's in the nature of open source to need to do this, or for that matter, multiple people working on the same project.
Decide the specifications of the project before you implement it. I've been bit by that more than once.
I disagree. Atmosphere is organized in a rational manner. It's componentized, and how it functions from a higher level is clear: it's not patching anything, it's replacing chunks of the OS with re-implementations. Each of these individual components are obviously in flux, but what they must provide for API is already quite well defined by nintendo. It's lacking in the documentation department, but that's to be expected at the moment.
No, it will not be more polished. It will be ready first, but it will not be more polished. Atmosphere is taking so long because they're doing it the right way, as in zero code patches but replaced components of the OS. This is in contrast to every other CFW in existence which uses some if not all code patches. These people have been doing reverse engineering, documentation, and programming for years. I find it hard to believe an unknown team who's contributed nothing can do a better job and isn't just leeching off open source work.
Also, paid professionals do not make for a better product nor code.