I tried this with a string measure but wasn't sure what you meant in terms of your comment about storing the variables as section variables. As-is with that boolean enabled the best I'm finding it can do with disabling parsing is just regular section vars like :W and such (expectedly, given the description), while the rest get parsed (including variables that themselves reference section vars).https://docs.rainmeter.net/manual/lua-scripting/#GetOption
There slightly is a tool that would have helped with this, GetOption used to have an undocumented function that was documented recently on the page.
What I ended up doing for different scenario I ran into following my post was reproducing an entire (necessarily lengthy) variable with hash-escaped strings (using balala's suggestion). Obviously non-ideal since it adds more redundant code but at least the variables get preserved for subsequent swapping via Lua.
Since, for some context, any dynamic changes (size, etc) don't get updated the moment a pre-parsed `GetOption` is swapped in as a replacement meter value, so the raw variables are needed.
So I'm using both workarounds from this thread: for simpler single variable names using a custom meter option, while for variables containing multiple variable names using an escaped copy under a different variable name and retrieved using Lua.
Statistics: Posted by Crest — 1 minute ago