Like the borrow checker story, Rust's separation of composition, delegation, and interface implementation is not to protect them from you doing them, it's to protect you from what will happen if you do them when you didn't mean to. You talk approvingly of Java interfaces but those were controversial at the time for exactly the same reason ("why do you need a separate keyword? Just write a class full of pure-virtual functions, it's the same thing").