Hey kwitt
I see what you are saying. It actually made me think of another solution that might work with a mix of content blocks and {% assign %} variables that I used when I was playing with OpenAI for a YouTube video. It might help and look cleaner.
You create the custom HTML and CSS for your IAM in a content block, but wherever you want your team to be able to update content, you add a liquid tag. You can see in my image I added {{brazeApiKey}} and {{brazeMessage}} as two examples.
Then you create a new IAM and insert this content block but at the top of the code you create variables that can be updated by your team. These will feed into the HTML in the content block. So, in my case:
{% assign brazeApiKey = "45783274934asdsa897d89sadas897da" %} (not a real key LOL)
{% assign brazeMessage="An image of a shopping cart full of groceries" %}
Each time a new user needs to use the template, they update the assign variable content and it will feed into the HTML content block. Might not be perfect for your use case but you can see in the second image it looks a lot cleaner to work with.
There's not much more detail in the related video but you might still get some value from it. My whole channel is around Braze content. 😊
https://youtu.be/M4cYr2ma19E?si=809k8APSAne2lKDf&t=121
