LrC always needs some sort of camera profile to act as a basis for its postprocessing of a Raw image.
This means, in the case of a proprietary Raw format you just have to wait until that camera model is properly supported by Adobe - at which point a range of profile choices will be there (Adobe Standard always, AFAICT, plus others too).
In the case of a native camera DNG, though, you don't have to wait for support because the camera has embedded its own profile as part of the standard. LrC is able to then extract and use this despite having no official "knowledge of" that camera. You get whatever result this embedded profile delivers.
I would imagine your intial processing was previously done like this. And suddenly recognition for that camera has arrived, and Adobe made profile(s) to be used by default.
In order to "get back" to how you have been editing before, you'll need to become able to deliberately employ that same embedded profile, that was previously used only of necessity. That means having it presented as a choice. It used to be that you could just choose "Embedded" in the profile selector but the whole profiles system has changed and I don't see that option presented any more.
BUT. If you download the free DNG Profile Editor (links for Mac and Window versions are here ) and open up one of your out-of-camera DNGs into that, you can then Export its camera-embedded Raw conversion profile as a suitably named "recipe" (.dcp file) - into the central folder used for such things. On closing and restarting LrC, this new .dcp file is detected by LrC. Now that "recipe" becomes available to apply inside the Develop module, by name, onto Raw photos from this camera. Either manually, or in a Develop preset, and/or setting it as the default profile to be imposed hereafter at import, instead of whatever Adobe supplied profile is currently being used.
AdChoices