Hey there.
I know “It’s the way it always has been” isn’t a great answer, but it’s probably the truth here. A lot happens in the backend when you bind the project through the UI and it has never trickled down to the scanner, nor any effort put into connecting the dots once the first scan of a project has been published.
We also have generally come from the opinion that project provisioning from the scanner is allowed but not ideal, as it can cause the proliferation of many projects where administrators don’t know where they came from. Maybe this is more of a SonarQube concern than SonarCloud where the concept of a “bound project” exists – but that’s the history.
All that said – you can vote for this card on our roadmap and leave feedback about why this is important to you: Automatic provisioning of bound projects - SonarCloud | Product Roadmap