You are right that the dhis2 integration team has put quite a bit of effort into the apache camel java integration framework in the hope that it will be useful and that we build up a body of shared experience.
But that doesn’t mean that anybody has to use it or even that other approaches are wrong. Python and nodejs are also two very popular languages for doing integration and we have seen many examples of successful use within the wider community of integrators.
What I would say is that while small scripts are often the correct solution to a particular problem, there are often complexities involved in integration, for example around error handling, concurrency, performance monitoring, orchestration etc which are not so easy to build in from scratch. This is where having a good integration framework (like camel) comes into its own and starts to deliver benefits.
A python framework which I have seen being used to good effect is Apache Airflow (https://airflow.apache.org/). Its not exactly an integration framework, but works well for this domain. The WAHIT team within WAHO have some good examples of it.
If you have more skills with nodejs you might want to look more at openFn (https://openfn.org). Lots of really exciting stuff happening there.
Sorry that is maybe a long answer to a short question. python scripts are not in any way “wrong”. If you are building more critical integration infrastructure then you might want to consider a more robust framework approach, even with python. We like camel, but there are of course others.