How to point app to promoted RDS replica without downtime or data loss

I'm using RDS with a read replica to perform some DDL operations on database schema, mainly adding columns to a table, without table locking or performance impact.

Now I want to promote the read replica to be a master on its own and point my application to the new promoted database, as described here. However, the docs say:

The promotion process can take several minutes or longer to complete, depending on the size of the Read Replica

I understand that, while the replica is being promoted, the changes from the source are not being replicated. So the new database won't have the records that were inserted during the replica promotion, and before I point my app to the new database.

Is there any way I can prevent the data loss while moving from one database to the other, apart from scheduling downtime in my app?