There is one very common misconception that flexibility always equals to complexity. I remember it especially from my Mental Ray days, when whenever I would mention that something in Mental Ray is unnecessarily complicated, a mob of die hard users would storm me with arguments like "But look how flexible it is, it needs to have all these controls and wonky workflows because in the
real production you often need to supersample the quantum waveform subsampler!"
In reality, settings can be easily divided into three groups: Visual (Scene look), Performance and Utility (System) and you can see how Corona render settings UI follows this division philosophy. While Corona team works at adding more Visual and Performance settings to make sure Corona can withstand all sorts of production requirements, they at the same time keep working on the smarter mechanism that allows them to remove Performance settings, and handle them automatically under the hood, to lift the burden of tweaking from users' backs.
If you need to render hair and skin, and Corona does not support hair and skin, then there is no question that hair and skin should sooner or later be added, because it becomes a matter of "I can vs I can not do the task with my renderer". Where as performance settings usually only balance output between speed or quality, they do not affect your image in artistic way. You never say "I want to keep my displacement less detailed because it looks better" or "I want to keep my render noisy/flickering because I like that style". So those can be removed without issues.
Then there is an issue of the amount of artistic settings. You will have to face the truth here, and realize you can't have your own renderer with exact feature set cut out just for you. If you do archviz, and don't use shadowcatcher or rayswitcher or hair or skin, that doesn't mean those things should be absent. On the contrary, they may save you migration to different renderer one day, when some more unexpected requirement comes from your client.
Now, it doesn't mean Corona will have to become as complex as V-Ray for example in order to become fully featured renderer. If you compare main features of Corona to for example V-Ray, you will realize there's not really that much more catching up to do. In general, it's just Hair, Skin shader and 3D volumetrics. Hair will be in form of a modifier and one new material, skin shader will be another new material, and 3D volumetric will be atmospheric effects. None of these need to have a single knob in render settings. If you are archviz user and will never use these, they will be out of your way.
Again, to clarify, the preconception that if Corona catches up with V-Ray, it will be equally as complicated is simply
wrong. Corona team is already 80% there, and if anything, they are actually cleaning the UI up. You can see the effort for example in the clean up of several settings inside of the separate system-wide settings window, where settings that are not often accessed got out of your way.
Now, there is a proposal on the table to do even bigger cleanup in one of the future version. Basically, right now, render settings acts as a centralized dashboard of the entire scene, while there are other renderers that adopted arguably better solution of putting most of the settings into appropriate scene elements. This is how it would look in practice:
And this is how render settings could potentially look after the cleanup.
If everything went well, we could eventually achieve a state where you would need to open render settings only in some rare cases, where you would need to do advanced things, such as setup material override, distributed rendering, etc... but if you were just after look development and scene building, you could stay completely away from them.