Yes....that is something I will be looking at down the road. Really what I am trying to do is determine which platforms I should target my service towards. I am working on a Machine Learning implementation that can test ideas really fast with the goal of being able to generate code which can run in an already built platform (i.e. NinjaTrader, TradeStation, etc).
In my limited view, no platforms perform the way I want them to, and I got tired of trying to shoehorn my ideas into existing designs that imposed artificial limitations. It's a learning curve and can be great for learning, but to go beyond, I think you need to free yourself and start from scratch.
I see you're also doing it ass backwards. Trying to find a platform to target.. After the fact. Now it may seem like that'll be your answer in the end, but the process is exactly backwards of what you should be focusing on: Who are your users/customer base? What are their problems, what do they need? What are they willing to pay? I'm assuming you're basing your income on future clients, and not pure edge to be exploited privately in the markets?
Yes, this is even more work! But may save you many dead-end attempts that lead nowhere other than as a learning tool. Also, if you can't face your customers, then you're not going to have much business relationship with them later either.
When you know your customer, then you may discover they prefer certain tools, but what if they don't want to use those tools? Making great tools is more about people, than the tools themselves.
If you make a backtester, you're already 70% there to make a live performing system. Also, how much do you want to marry external tools and their inner workings? Finding the right APIs might be preferable to finding the right platforms.