I see those arguments but:
o the new feature speed is only gained after a complete re-write
o in 80% of businesses people cost >> than hosting
o re-writing always introduces more bugs
The only time that I would agree to something like this, is to get all my teams onto the same platform. Again, thats not a technical decision though.
ES6 to TS is more refactoring than a re-write. Just start with the core library and some TS linting and fix things as you go. The time it takes to 80-20 a microservice project into TS is usually less than it takes to hunt down a confused type bug (ie. someone thought this was an array but it's a string).
This is not a "re-write":
function(param1, param2) {}
function(param1: string, params2: number) {}
Even speed alone, though, can help substantially reduce other more tangible costs; if your TypeScript backend is faster than your non-TypeScript backend, then that translates to needing less server resources to achieve the same result (and/or being able to handle heavier loads without needing to upgrade or expand your server resources).