OP has provoked the following question. Whether it is reasonable for a prudent head to have the same SEED on different wallets? Sure, that is a measure to take down the overhead of the wallets management but at once not at its shiniest to the safety of the funds. The last sentence is in a way my sort of answer to OP.
there is absolutely no reason to do something like that in real world. you will never find any design that needs the same set of private keys in 2 exact places at the same time.
the real world applications are either private keys (which is the seed) in one place, usually offline; and the public keys (the extended pubkey) in another place as a watch only wallet.
or in some complicated scenarios like a company with different layers, an exchange,... you may see extended "child" private keys but no the master key itself. and even the children are still in one place not multiple.
