The issue here is the version of ChromeDriver.exe we package. The hard dependency is there. If you download the latest ChromeDriver.exe from Selenium and add it to your project (make sure it gets copied to the /bin directory), Fluent won't unpackage its own older copy and the mismatch problem should go away.
We are working on making this more transparent to the user and pulling latest into the project on setup, rather than packaging it into our DLLs.
(Author of FluentAutomation)