As usual, all of these "use cases" suffer from the problem at the boundaries (see also Oracle problem), namely that you can automate everything on the blockchain you're using, but once you're back in the real world you no longer have any guarantee. Your new layer of abstraction just leaves you with a more brittle system.
* insurances: you still need somebody outside the smart contract that needs to connect it to what happens. You've just moved the trust from one place to another, and you're not better off.
* transferring money is faster in many countries than it is with (e.g.) BTC when you include the wait for the confirmation blocks. It's also bound to become faster and cheaper, while many blockchains (especially BTC) seem stuck with their processing time. Even countries with slow bank transfers now tend to have a fast solution, like Zelle in the US. Add problems like volatility of the cryptocurrency with the respect to the currency that actually matters, high (and volatile) fees, and transfers via cryptocurrencies is only attractive in a few countries and will only remain so as long as these countries do not improve.
* with art you again have the same boundary problem: the blockchain you use doesn't know what's happening, and only the law will resolve your conflicts.
> efficient, transparent and enforce standardization
So far the blockchain systems have been less efficient than non-blockchain ones they purported to replace, see the usual comparison with the Visa network for example.
Transparency and standardization are orthogonal to the use of a blockchain: using one doesn't mean you can't be opaque or follow any standard.