I have been looking into this as I have seen the error on my server occasionally. I am now explicitly logging events around the code and the "editor.config.vbPluginPath". Identifying the sequence that causes the issue is the key to solving this kind of problem. I have not been able to manually trigger the sequence that leads to the error.
In my opinion:
Most likely vb was trying to do something similar, but did not have much success -- which is probably why it is not fixed. At some point you just have to move on to more important issues.
Copy the directories if you want the error to disappear and I will post an update if I find something. Since the error happened so infrequently on my board and I have had no complaints on functionality (at least not reported). I usually under these conditions just go on with my life.
However, I do understand your frustration and maybe my event logging will come up with something. Have a good one.