Most of these headers exist to make a whole class of attack stop working without you changing a line of application code. HSTS stops a visitor on café Wi-Fi from being quietly downgraded to plain HTTP. A working Content-Security-Policy means that if someone does manage to inject a script into your page, the browser refuses to run it. Clickjacking protection stops another site loading your page invisibly and tricking your users into clicking buttons on it. None of them fixes a bug, but each one limits how much damage a bug can do.
They are also the first thing anyone checks. Customers’ security teams, auditors and security questionnaires look at your headers because they can do it in seconds from outside, and a site with none of them sends a signal about everything else. We learned that ourselves: the first time we scanned SecQon with SecQon, neither our website nor our API sent any of the five main security headers.
A header being present is not the same as it working. An HSTS max-age of a few minutes, or a CSP that allows scripts from anywhere, looks fine on a checklist and protects almost nothing. That is why SecQon reports ineffective values as findings in their own right, with the exact header in the evidence.