> This delegate translator should work with various translator (JDBC, File etc)
Generally our recommendation for a JSON data binding is to use OData. In the case of doing this in a custom way as a delegating translator, it really matters what the condition is as to whether you can split it and then it matter what the source is as to whether the construct will be supported. If at all possible the JSON binding should be done at a high level (such as being done with JSON functions in a view layer), so that the lower level processing doesn't require special handling.
> Another ask is to remove the Comparison from the Condition tree and have it evaluated by the delegate translator.
Here again, this sounds more like what the OData layer is providing - a general binding to JSON/XML. You probably don't want to go down this path in your own layer.