Will your feature suggestion eliminate X% of security vulnerabilities of a given kind in current C++ code? If yes, please be specific about the classes of bugs that would go away, with an example or two (especially a link to a real CVE or two).

No

Will your feature suggestion automate or eliminate X% of current C++ guidance literature? If yes, please be specific about what current good guidance this helps make the default, and/or what guidelines we would no longer need to teach/learn or that would be simplified and how, with an example or two (especially a link to a real "Effective C++" or "C++ Core Guidelines" guideline or two). For ideas, you can refer to my CppCon 2020 talk starting at 10:31 where I summarize a categorized breakdown based on over 600 C++ guidance literature rules I cataloged and analyzed.

Not standalone, but it will enable different types of experiments with cpp2, which will hopefully improve adoption

Describe alternatives you've considered.
There's nearly always more than one way to improve something. What other options did you consider? Why is the one you're suggesting better than those?

Manually copy paste the included/imported files which the generated file references.

Wins

• able to try out cpp2 on leetcode/codeforces/timus. This is how I learned cpp initially and I'd like to repeat that experiment with cpp2
• able to send a single cpp1 file + the corresponding cpp2 file to a colleague so that they can look at the cpp2 file, be impressed by it, and verify that the corresponding cpp1 file compiles to expected output without making any changes to their dev env