It seems odd to use different timeouts (and timeout factors) depending on whether the Python RPC proxy is used, or the bitcoin rpc command line interface.
Fix it by using the same timeout.
This can be tested by introducing a timeout error and checking it happens with and without --usecli after the exact same time.
Example timeout error:
0diff --git a/test/functional/mining_template_verification.py b/test/functional/mining_template_verification.py
1index de0833c596..e0f93a2b1e 100755
2--- a/test/functional/mining_template_verification.py
3+++ b/test/functional/mining_template_verification.py
4@@ -173,7 +173,7 @@ class MiningTemplateVerificationTest(BitcoinTestFramework):
5
6 self.log.info("Submitting this block should succeed")
7 assert_equal(node.submitblock(block.serialize().hex()), None)
8- node.waitforblockheight(2)
9+ node.waitforblockheight(200000)
10
11 def transaction_test(self, node, block_0_height, tx):
12 self.log.info("make block template with a transaction")
Example cmd: ./bld-cmake/test/functional/mining_template_verification.py --timeout-factor=0.1 --usecli.