A better metaphor would be; I want to boil some chicken to make a healthy dish and I have a pan full of boiling water... Then just as I'm about to put the chicken inside, the head chef stops me and tells me that I need to pour oil into the pan.
I protest; "But sir, there's no need, I'm making boiled chicken, not fried chicken... This isn't KFC."
"Do as I say" says the head chef.
So I reluctantly pour some oil on top of the water, then I add the chicken. It splashes around a bit, no big issues, and the chicken comes out OK; slightly of greasy but not noticeable after adding the seasoning...
"See, it all worked out, aren't you glad you listened to me?" says the head chef.
If you start by just throwing all the crap you want into a pot and afterwards try to remember what you added and how long you cooked it for of course it's going to be a lot of extra work. TypeScript requires a methodical approach which over the long run makes it easier for the entire kitchen.
But parent is saying that you should recognise that you're opting yourself in for a harder time by ignoring typescript at the beginning, and then trying to retrofit your way into type safety. That's definitely going to be more difficult and frustrating.
So either don't use typescript (which is fine fine - no one here cares about the programming language you use), or, use it 'properly' from the beginning and work with the tools you're using rather than against it.
It sounds like your process is a bit of a drag on you and I think you should improve it.
This is akin to throwing water over an oil pan fire, then being frustrated at the water for your house burning down.
You need to either use the Typescript way throughout your dev process, or not use Typescript. Both of those options are valid, but you're currently doing half of both, resulting in unnecessary frustrations.