This is how frameworks arise. Reusable libraries (often opinionated) to accomplish things with less effort. So you are basically advocating framework usage, even if its your own in this instance. Perhaps you should document and release it, get it unit tested, open sourced and peer reviewed and then it might be up to standard with some of the other more modern frameworks that are already out there!

This happened to me about a year ago specifically for razor files. It turned out in my case that it was resharpers syntax highlighting that didn't support razor in mvc core projects yet. I disabled resharper for razor files (somewhere in resharper settings you can tell it to ignore .cshtml files) and all the crazy squiggles went away.