Use slave to change innodb_file_per_table (2 replies)

We have a case of the ibdata1 file having gotten large. We are looking at the processes to reduce that file. There is plenty of good samples of what is required to be done to shrink the file via mysqldump.
My question is can you set up mysql replication with innodb_file_per_table enabled on the slave and then once it is synced switch to the slave as the master.
Create a new slave back on the original master server with the new innodb_file_per_table and once sync is up to date switch it back as the master if so desired?
This would appear to minimize the downtime to negligible when wanting to change this parameter and clean up the ibdata1 file.

I cannot find any articles, and I cannot understand a reason as to why this cannot be done, so could someone please enlighten me?

Thanks for the enlightening

Peter