I don't think even having multiple dynamic prompts removes the benefit, although for sure it gets a lot more complex to parse and understand as a human. Since

I don't think even having multiple dynamic prompts removes the benefit, although for sure it gets a lot more complex to parse and understand as a human. Since the prompt(s) has/have to be rendered at some point though, even if at runtime immediately before use, it could still be made displayable to the user. Assuming this data is already in the database, it doesn't seem like an overly difficult feature to expose. And if it isn't, adding a column to capture it doesn't seem overly difficult either. Regardless, if there's a "view source" option available on GPTs that opt for it, I'm likely to check those out whereas an opaque one I'm likely going to pass on. Even if it won't work for 100% of cases, it's still an improvement to the status quo.