I can’t answer that question directly and unable to test it at this time. However this information may assist you in your testing.
The REPLACE keyword says, “remove any existing rows before starting the load.”
You can’t stop a commit from occurring during SQL*Loader loading, but by setting the ROWS= parameter to a large value, committing can be reduced. Make sure you have big rollback segments ready when you use a high value for ROWS=.
I am wondering, if by setting ROWS= to a high number (depending on your system specifications along with the number of rows you are working with and size of rows) if this might work for you.
Please let us know if this helps you in your endeavors.