Hi David,
This makes me think of a few other past discussions (e.g. this one) where the use-case was indeed not best covered via SonarQube APIs. Yes SonarQube can process coverage information, however its core capability is about the detection/tracking of bugs/vulnerabilities/code_smells, and that’s where you’ll see APIs’ focus and intent.
If you think about it, SonarQube is already itself importing coverage data from external tool. So when I read your plan:
I’m tempted to ask: why not just query the data/reports from the coverage tool directly ? which is anyhow the raw data that SonarQube leverages.