I mentioned typescript and react (meaning jsx actually) because browsers run javascript.
So the browser will have to be able to make a mapping from javascript -> jsx -> typescript in order to report correctly what was covered during the execution.
That mapping is going to happen though regardless if it is a headless or real-user interaction. I don't think these tools are going to help with mapping unless you know what kind of interaction you want to simulate, and be able to map the entire interaction. I think tracing and logging tools would be a lot more useful and appropriate for those types of scenarios. I do think they can help with e2e testing, just not inline with the frameworks you mentioned.
So the browser will have to be able to make a mapping from javascript -> jsx -> typescript in order to report correctly what was covered during the execution.