Thank you. The problem I have with this is that looks to me as bad design. Either you want immutable transactions, in which case, use a blockchain, or you want the administrator to have control, and therefore you can do off-chain internal transactions.
For example, the plugin already gives you the ability to cancel a transaction. What happens if you have already recorded its hash somewhere? Does the hash prove something? It should not. Also, nobody is stopping you from editing a transaction via MySQL.
Internal DB transactions do not offer the same guarantees that a blockchain does. If you were to do what you suggest, you would be making promises you can’t keep. In other words, you might give the impression that these transactions are immutable and censorship resistant, when in fact they are neither of these things.
I believe this is why nobody else is doing this. What do you think?