NoTargets does not work with multi targeting when project extension is .msbuildproj

Minimal, Reproducible Example

Source: https://github.com/bash/MSBuildNoTargetsIssueRepro
Failing Travis build: https://travis-ci.com/github/bash/MSBuildNoTargetsIssueRepro/builds/152979950
Error Message:

/usr/share/dotnet/sdk/3.1.102/Microsoft.Common.CurrentVersion.targets(1175,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [/home/travis/build/bash/MSBuildNoTargetsIssueRepro/MSBuildNoTargetsIssueRepro.msbuildproj]

Possible Workaround

I believe the issue is that Microsoft.Common.CrossTargeting.targets is never imported when the project extension doesn't correspond to a language.
My workaround sets the propertyLanguageTargets to a custom file, that imports CrossTargeting.targets

Start with the linked minimal reproduction and the failing Travis build, then inspect LanguageAgnosticShim.targets and how the .msbuildproj extension selects its targets. Compare the workaround with the normal multi-targeting path and verify that the reported MSB3644 error no longer occurs for this project extension.