Uodate: I was mistaken. Daisylink is in fact using native SoftwareI2C and not the managed implementation!
I have been looking at the DaisyLink protocol quite in-depth lately and one of the issues I see regarding performance is that the Hydra and Cerberus (probably others as well) do not provide a native implementation of the Software I2C for the DaisyLink protocol. This is unfortunate because the GHI firmware does provide a native SoftwareI2C implementation which could probably be leveraged to provide this implementation to the DaisyLink module.
So my question to GHI is, do you for see that you will provide an implementation of the SocketInterfaces.NativeI2CWriteReadDelegate on the Socket class? This would undoubtedly give better performance than relying on the current managed implementation, though
I do not know if any of the other Gadgeteer users are experiencing DaisyLink latency due to the reliance on the managed implementation, so the win might be very small, but I thought I would ask especially since 98% of the code is already there and probably only requires a few minor tweaks.