The original intention of arbitration is to enforce "Intention of Code is Law" to enable recovery of funds due to the result of bugs resulting in the lost of funds similar to the DAO hack case on Ethereum
This is not true. "Intention of Code is Law" was invented by Dan Larimer after the blockchain was already launched. It wasn't included in the original designs.
Other methods of ensuring securing your funds already exist, such as multi-sig, staking and multi-permission structures, and cold-storage with hardware wallet access.
Yes, but this is not contrary to base-layer arbitration. We can have them all: base-layer arbitration plus all the nice security features. A blockchain which uses only some of the security features available will be always less secure than one which uses them all, including base-layer arbitration.
In my view, on the base level, transactions should be immutable. A blockchain that is not immutable is worthless — nothing more than a typical cloud database system.
Yes, and in EOS transactions are immutable. All transactions are immutably recorded to the blockchain: stealing tokens/accounts, ECAF's ruling and BPs enforcing it. Nobody is removing or altering any transactions in the blockchain. There are only added new transactions, and they are authorized and made in accordance to the rules of the network.
Limiting the power of BPs is extremely important, just like limiting the power of governments as well, whether or not they are being good at this point in time.
That's why we have ECAF. It helps us to separate powers. Without it, BPs would to both rulings and enforcement. That is usually very bad idea. Now we have ECAF which makes the rulings independently so it limits the powers of BPs.
My proposal would be to simply disallow all transactions from a "protected" account to a "base-level" account that cannot be subjected to arbitration.
This would create two totally different ecosystems on the blockchain. It doesn't make much sense. A better way would be to create another blockchain with different rules.
Yes, "Intention of Code is Law" is Dan's attempt to fix the flaws of the original design, and I do agree with him. It is nature that blockchain projects experiment, improves, and evolves over time -- especially so at its infancy.
My view on immutability is that transactions have to be immutable base on private key -- i.e. funds transferred cannot be reversed nor stopped by any other private keys.
I do not understand how making the EOS ecosystem more flexible doesn't make sense, perhaps you can elaborate the reasoning behind this.