Cleanup incorrect assert after TS-4403

Now that we allow for some records to persist in the case of failure, the records in this path are not always in the 0 state-and therefore this assert doesn't work. Regardless this assert is a bit useless since the replacement of multicache with RefCountCache- as we aren't clobbering memory all over creation-- so the need for these types of asserts is significantly reduced.