The question is "do you want to know about a valid CVE if there's no patch available"?
For high security environments, the answer might be yes (you want to evaluate individual patches to see if they impact your application)
For many environments the answer is likely (as is the case with OP) no, you only want to know about issues for which there is an updated package available.
Interestingly (well to me :) ) more established scanning tools (e.g. Tenable Nessus) default to "no" on this question and container scanning tools mostly default to "yes". (I did an example comparison https://raesene.github.io/blog/2020/11/22/When_Is_A_Vulnerab...)
The important part is that your organization makes an informed choice about which works best for them.
As a sidenote there are also differences in severities and how vulnerabilities are counted (e.g. if you have multiple issues in a package do you count each one or just count once for that package) which can lead to different numbers of issues being reported by different scanners. https://raesene.github.io/blog/2020/06/21/Container_Vulnerab...