Keybase potentially interfering with other Dokan based programs

I have a number of machines all of which have Dokan installed for a project I'm working on. After installing Keybase on one of the machines the Dokan portion of the other program seems to be responding quite slowly (more details below). To try and explore this a little more I uninstalled Dokan on two of my machines and reinstalled Dokan 1.0.0-RC3. On the machine with Keybase the other program has Dokan issues, on the machine without Keybase everything is working as it should.

Two questions to help me work through this problem:

1. Can I safely uninstall + reinstall Keybase and keep my device credentials in tact, or at the very least still associate my existing device name with a new key without a full Keybase keychain reset?
2. Have you used any other Dokan based software along side kbfsdokan, and if so have you noticed any issues?

-----------Details about particular issue I'm experiencing--------------------------------------
The other program doesn't seemed to get called by the Dokan hooks as quickly. This is particularly obvious when writing to a file. Diagnosing exactly what is going wrong may take a little time but it currently looks like Dokan is either spending more time than it should verifying the ends of writes, or it is performing operations slightly differently or out of order.

If it's helpful I can explain what I see in more detail, but my guess is that there is just a corrupted state issue with Dokan and I only need to figure out the best way to reset the state (without just wiping my machine).

No source file, test, or entry point is named. Start by reproducing the write slowdown on machines with and without Keybase and Dokan, then compare the observed hook timing and operation ordering. Done means identifying the interaction or documenting a reliable reset or compatibility path.