The minutes do not say anything in that regard and this was not my understanding from the conclusion. And, as far as I understand, @MrKevinWeiss understood it like that as well?
Where is the harm in keeping the compile-time configuration? On the contrary, I see huge drawbacks when we take the step back from all the configuration exposure @jia200x and @leandrolanzieri did in the beginning.
My understanding was that the dependency modelling and the resulting CI testing was what pains most maintainers. The Kconfig compile-time configuration is so low-profile, I think its worth keeping it and porting it to whatever solution comes up as an alternative to the Kconfig dependency modelling. The latter btw was discussed: