Sorry but we don't currently have anything like that.
It is something we may possibly do in the future but I have mixed feelings about it because the idea of doing more database hits to replace tokens in content does not appeal to me, so it depends on what the tokens represent and how expensive it is to look up the data to replace them and how many hits to the db would be required, etc. To me it seems like it could easily be over-done and cause performance problems. If it is just replacing them with html fragments then I think the content templates meet this need already and are efficient because there is no lookup to render them since they go right into the content.
Maybe if you describe in more detail the kind of use cases this solves for you then I can ponder it better.