No, because the human does not need to process the entire screen contents with every frame, only the delta from the last frame (usually). Therefore getting those deltas into eyeballs as quickly as possible increases how quickly the human can interact with the computer.

There are cases where this makes a big difference.

For a dramatic example, consider the VESA framebuffer console, a slow serial link, or a bad SSH connection with a good CPU on the other end.

With enough terminal output it will bottleneck whatever you're doing. Sometimes extremely dramatically so. To the point of adding hours to a task in really bad cases.

For such situations, it often helps a lot to run remote tasks in something like screen and only switch to it to check progress once in a while.

The reason is that the limiting factor absolutely should be the human, so if the computer is slow enough that the human can possibly notice it, it needs to be 10x faster.

This is more about responsiveness than batch-processing speed.

Makes using them more enjoyable.

Hi, I'm the author of almost all of those VTE performance improvements. I wrote them because the latency in gnome-terminal, which I've used for well over twenty years, was starting to make me miss-type due to how slow the feedback was on Wayland.

Simple as that.

It only matters to a certain point. After the latency is below some threshold it no longer matters.

However because how Linux graphics system was developed, there is a lot of extra latency and bad software out there, so it might be noticeable.

It's mostly just a matter of comfort. Characters appearing very quickly after you type them is more comfortable.

Not if you're tailing log files.

Lower input lag enables flow state. Can't explain it. You have to feel it.