Instead of master_use_gtid=current_pos , create gtid_slave_pos_from_master=1;

Make an option to CHANGE MASTER that updates the
gtid_slave_pos at_the_time_of_that_command_only, like a one-shot
master_use_gtid=current_pos. Eg. something like:

CHANGE MASTER TO master_host=xxx ... gtid_slave_pos_from_master=1;

The idea is that to make old master a slave, a CHANGE MASTER command will
usually be needed anyway. And that is the point at which user wants the
binlog position to migrate to the slave position.

But with the current master_use_gtid=current_pos, this migration happens at
every future slave reconnect, which is very much not expected, and users are
all the time confused that a random manual transation on their slave later
makes GTID replication break.

Credit:- Kristian