Many years ago when I was in University developing with the DirectX SDK the first thing I and others would do on any computers we were using would be to disable C-States and other power saving technologies because stepping through C-States takes a certain number of clock cycles and the 3D software we were designing required all the resources we could access.
In principle the software Battlefield 2042 is no different. It is both intensive and dynamic in its execution with each round being different from the last with regard to: the number of assets loaded, where players will be, what they will be using, what effects you'll see and where you'll see them from as such the frame stutters may not occur in the exact same place or scenario as it did before.
It is also possible that an update to the game may change the frequency that the issue is perceived but that does not mean that the CPU isn't engaging in a C-State while you play. It could also indicate that your CPU is able to process the necessary instructions with fewer resources without causing a noticeable pause, however as mentioned in my last post C-State issues can manifest in other ways such as: mouse input lag, sound distortion, loss of frames and can in my opinion contribute to program instability and an unstable overclock and as such this is why I recommend disabling it.
The solution is reversible. The only reason I can think of to keep C-States on is if your computer is for office work or light entertainment as the resources required to perform such tasks are small and as such you would not notice a difference in performance.
You should also confirm that your documents folder is located on an SSD drive and not on spindle based storage media as the game seems to be saving some kind of cache in that directory and as such you may end up with invisible models if you are storing the directory on the latter.
