Does SSR and CSR createCache need to be set with identical options?

[TimeDropsSB]

I have a NextJs 14, MUI v5, and Emotion v11 app and my issue is there is a style tag generated by Emotion that disappears at random times while navigating and interacting on the client-side UI. Right now, I have two createCache instances being used: one on the server and one on the client. I don't know the exact reason for the issue with the disappearing style tag but I've managed to get it fixed by setting speedy: false on the server and client cache.

Since the server cache isn't the issue, I would like to be able to set speedy: false only on the client-side. Would there be any issues with using createCache set with different options for each instance?

[Andarist]

speedy shouldn't affect this anyhow - it's actually a CSR-only setting and can't affect SSR styles. That said, the options should kinda be identical on both sides - other options, like key, are very important for deduplication and hydration purposes.