We're exploring whether or not we can support Airbyte connectors on our upcoming Meltano Cloud offering. As it stands we have some community members running Airbyte connectors in their production environment with Meltano and they seem quite happy with it!
As with anything there are tradeoffs though - gaining the ability to have a connector in a non-Python language comes with the overhead of running (likely) Docker-in-docker. Also, connectors not built on our SDK[0] are missing out on some nice features like batch message[1] support (for bulk loading) and stream maps[2] for inline data transformations.
It seems to me that it's sort of a 'picking winners' approach, in that someone in Chile is picking companies to give money to. More broad based approaches that simply make taxes/bureaucracy/financing etc... easier for everyone are something I would see as more favorable in some ways.
That said, it doesn't seem like a great deal of money, and in terms of a "publicity stunt", it certainly seems to be effective.