I think it's just part of the natural lifecycle of products.
The purpose of a committee is not to keep the API fresh by rethinking the design. They're bad at it, but that's okay because it's not their goal. The purpose of a committee is to change the current API as little as possible, while smoothing out the concerns that stakeholders on both sides (users and implementors) have. It's something that individuals are often really bad at by comparison.
The strcpy() function has to stay, because the committee cares about legacy code. This isn't a problem, because it's one function, the namespace is big, and you can always switch to Go/Rust/C#/Haskell/etc. if you don't care about legacy code.
The purpose of a committee is not to keep the API fresh by rethinking the design. They're bad at it, but that's okay because it's not their goal. The purpose of a committee is to change the current API as little as possible, while smoothing out the concerns that stakeholders on both sides (users and implementors) have. It's something that individuals are often really bad at by comparison.
The strcpy() function has to stay, because the committee cares about legacy code. This isn't a problem, because it's one function, the namespace is big, and you can always switch to Go/Rust/C#/Haskell/etc. if you don't care about legacy code.