EDIT: @ethankopit I attempted to recreate the scenario above to submit to Support and the functionality worked as intended! Perhaps there was user/account error on our end that caused the scenario I described.
I will keep an eye out for any other instances of unintended behavior, but as it stands, I believe this is working correctly.