Answer
No — documented practice is to keep using the same topic branch created for the customization-upliftment-preparation step all the way through to merging the uplifted customizations into the release-update branch, not to split the work into separate branches per step, even if both would technically contain the same code files.