This approach is brittle.

Consider the recommended approach to scaling a LoopBack app: 4 processes running LoopBack with memory dbs pointing at the same file... 

The current approach breaks down as the file may be modified by other instances.

The only way to really support this - is to remove all state from the adapter.... basically loading the file every time it changes.