I think there are two conflicting forces at work here. Working against integration is the fact that VFP is probably the highest-level general purpose programming language MS sells. The relatively small market and large effort to convert (look at the current massive runtime libraries) will cause VFP to lag the other VS members.

OTOH, VFP already has a long, successful history of "compiling" to intermediate p-code (even on the Mac!).

There have been calls in the past for a "cleaned-up" version of VFP, stripping out legacy support (@...SAY, etc.) However, if the new approach is to focus on JIT compiling, I see no reason to strip out macro expansion, which is a major benefit to using VFP in the first place.