Can the temporary table name created during clickhouse-copier copying process be a non-fixed name?

[Tiakon]

Due to the lack of real-time data replication feature in clickhouse-copier, I have enabled two instances of clickhouse-copier for the same table - one for real-time data replication and the other for historical data replication. When both instances are used simultaneously, data loss occurs and is accompanied by the following two exceptions:
Exception 1: <Error> Application: Code: 517, e.displayText() = DB::Exception: Received from cn-xxx-xx-xxx-04-1id9:9100. DB::Exception: Cannot assign ALTER PARTITION, because another ALTER PARTITION query was concurrently executed. Stack trace:,
Exception 2: <Error> Application: Code: 60, e.displayText() = DB::Exception: Received from cn-xxx-xx-xxx-04-1id9:9100. DB::Exception: Table dispatch_db.dispatch_analysis_local_piece_0 doesn't exist. Stack trace:.

Later, it was discovered that the fixed temporary table name during the clickhouse-copier replication process was the cause.
May I ask if it is possible to remove this restriction in the new version?