We already use something like the blockchain to store InstantX transactions and where the users promised the funds to go. This "blockchain" is managed by quorum messages; you can't add to it as a user. If any new blocks or txes conflict, they are rejected by the entire network.
That is what this datastructure is for:
https://github.com/dashpay/dash/blob/master/src/instantx.cpp#L23
You can't cause a reorg, because you can't get the block in question approved by the network in the first place. Miners blocks have to qualify to get accepted by the network, it's not as simple as the Bitcoin system.
Even if you could do a reorg, IX only goes up to $2000 worth of coin, a reorg would cost more than that in processing power to pull off. You can't simply sent the conflicting transaction to a miner, they have the list of IX transactions and already will side with the masternode network.
https://github.com/dashpay/dash/blob/master/src/main.cpp#L2973
Given that you can't get a block approved with a conflicting transaction, it can be trusted 100% of the time. These attacks are more theoretical, where the double spend attack that we're stopping is trivial to pull off. On Bitcoin anyone can double spend against you by submitting two conflicting transactions to separate edges of the network, there is no question our network is safer to do business on because of this.
For more information read 4.2, 4.3, 4.4 and 4.5:
https://www.dashpay.io/wp-content/uploads/2014/09/InstantTX.pdf