>>Using VFP dbc how can one modify or build an application so that there will be no need to hack the registry because of potential problems with SMB2 and SMB3?
>
>No.

definately not true.
Put dbf behind a web server, either from Rick or with foxincloud ;-)

Now to area perhaps more to the liking of OP:
I am uncertain if SMB will kick in if all vfp processess run in the same logical machine.
VMs shoukd be in trouble, but perhaps some app allows something like MSTSC or web access to one of many processes running in same adress area. Tests under SMB1 did not show the degradation of "second network machine in table" when different exes on same machine were hammering tables.

//upd:
another option is to have all machines working on local tables and replicating / syncing them via HTTP or FTP.
Rainer once went that way with an app with massive tables but relatively tiny writes compared to reads - not in LAN, but across different countries, when tunneling, more modern ways of accessing were unknown amd speeds were not speedy ;-)