Parse AC expressions stored in backend as strings

It would be very useful if there were a way to tell Wappler to treat a string as
a variable/expression to be parsed and evaluated where it would normally treat it as literal text. Eg if a string such as:

{{field_1}}
or perhaps including HTML and literal text:

… is stored in a database and included in a page, it will appear as literal text, whereas it might be hoped/expected that the string would be evaluated, as if it had been hard-coded into the page originally.

There are many situations where this would be useful. @sitestreet expressed a need for such functionality in this thread, as did @Mr.Rubi who mentioned:

Such a function would really be useful in cases where it is necessary to implement CMS functionality in a project

In a fairly recent thread @updates needed this or similar functionality, and it seemed perhaps that @patrick was able to offer a solution - or at least a solution which might be related to the current request. If there is already a solution, albeit not yet implemented in the Wappler UI, it would be very helpful to have more information about this, until the feature can be fully implemented (if possible).