Yes, what you’re referring to is the IDbCommand.CommandTimeout property. However, there is no way to set this in FactorySQL. We found its implementation to be unreliable across various database connectors, at least back then.
Your best bet, if there really is no way to improve the table locking, may be to have FactorySQL (or your procedure) write to a buffer table, and then have some daemon move the data from there into the final table(s).
Regards,