It worked in Core Config 2.0 because they never actually localized it. All the text strings are in the .PS1 files. Corefig 1.01 doesn't work because I mostly implemented localization but misread the documentation. I found things that said that if a subfolder match for $PSCulture can't be found that it would default to the first set that it did find. What wasn't clear was that it has to be in the same folder for automatic selection to work. I had assumed that since the only set it would be able to find were those in the en-US subfolder that it would automatically use them.
I think there is a way to override $PSCulture but that's not something I would ever ask anyone to do. There is no point in adding localization support if I just force you into an en-US culture. Having the en-US .PSD1 files in the root folder is the actual solution for any language that doesn't have its own localization files. I will rebuild the package into 1.0.2 so that the en-US versions are in the root.
On that note, I am absolutely accepting submissions for languages other than en-US.