Instance ID generation means multiple different carousels embedded in page use identical presets

This is a kind of weird edge case that relies on a somewhat unique combination of modules, but I'm wondering if anyone else has run into this.

I'm using Entity Embed to embed a custom entity type that uses Owl Carousel inside the WYSIWYG area of another page, using Formatter Field and Formatter Field Preset to select the preset to be used. When doing this, the instance ID that is generated in owlcarousel_fields_field_formatter_view is identical for all instances, meaning that when the carousels are rendered, the same presets are used for all carousels on the page, and they look the same even when they shouldn't.

I don't think that setting the carousel instance ID to owlcarousel-fields-($instance['id']) generates a unique enough ID for this particular case. I'm not sure if using this particular syntax has any special meaning to the devs, but I have found that something like owlcarousel-instance-($entity_type)-($entity_id)-fields-($instance['id']) allows us to get the entity ID of the embedded object into the carousel settings as well, thereby ensuring further uniqueness. In most cases, it shouldn't add too much length to the instance ID.

I've created a patch to demonstrate what I mean. Probably not the highest priority, but if someone could take a quick look at it and let me know if I'm barking up the wrong tree or not, that would be great.