If it's really a c++ feature issue, it would make sense if they checked msvcp140.dll instead. Setting arbitrary version without understanding what's the problem was is not great, do we have this issue in our msvcp140? Does it correspond to newer or older behavior?
And if this is in fact a problem that's not fixable at application side, e.g. by never using constructs that supposedly cause the issue, "correct" way seems to me is to bundle crt modules of a matching version. Or asking user to install updated redist package.