Best practice to scan a build whose files depend on a config

Thank you for these answers.
If we scan to a project per build config, what about the project’s number of issues ? I mean that if a bug is spotted in a file that is common to two configurations, will it appear in both projects, will it be counted twice ?

Instead of creating one project per config, can I push to a short lived branch per config (say for example my_dev-linux and my_dev-xbox) ?