Do extension settings reference or depend on the extension's internal uuid?

Do extension settings reference or depend on the extension’s internal uuid e.g. from `storage/default/moz-extension+++<UUID>/`? Would it be problematic to sync a profile’s storage/default/ with another (or at least an extension’s settings at storage/default/moz-extension+++<UUID>/) between profiles?

I’m looking to keep extension settings of my various sandboxed (via firejail) profiles consistent, e.g. settings from a “master” profile synced to the rest of the profiles. Not all extensions support Firefox’s sync feature to sync their settings (and I also prefer to self-host both the Firefox account server and Firefox sync server but have not found a straightforward way to set both up).

Basically, is there a straightforward way to manually sync extension settings across profiles in a manner that is “safe”, i.e. the data that is synced is profile-agnostic so there wouldn’t be potentially security/privacy concerns? Are extension settings portable across profiles or can they be dependent on a specific profile and therefore not appropriate to sync in such a manner?

Yes, at least IndexedDB does.
Last time I’ve tried to copy corrupted DB of a temporary loaded addon into a different Firefox profile (into some \storage\default\moz-extension+++7556ad3f-f005-4ded-a4f5-89512f881efe folder), it failed with this error in the browser console:

12:59:31.134 Quota The name of the origin directory (moz-extension+++7556ad3f-f005-4ded-a4f5-89512f881efe) doesn’t match the sanitized origin string (moz-extension+++f3fecdff-5c3b-4a82-9233-91194e4d7807) in the metadata file!: ActorsParent.cpp:3981 2

But I don’t have more info… I only know that copying whole profile helps.

Firefox’s browser.storage.local is built on top of IndexedDB. Given what @juraj.masiar shared, I expect the answer is yes, it would be problematic to sync a profile’s storage/default/ or storage/default/moz-extension+++<UUID>/ directory with another.