The Rust RFC process does not seem as amazing as I initially thought

I am a relatively new rust programmer, so this opinion might not hold a lot of weight but this is how I feel after I have gone through some RFCs.

Initially the Rust RFC process seems very welcoming. Anyone can open an RFC as long as the idea has merit and is well fleshed out. People develop and refine the idea over time, RFC gets accepted, implement in nighty, further refining, go through a stabilization period lo and behold you have added a new great feature to the language. The language in the rust contribution walkthrough makes it seem amazing.

Initially on my time learning Rust and looking for some features, when I found RFCs that address it, I would be happy because it means it is possible they might get added some time in the feature. But now, I just give up hope of that happening anytime soon.

This seems like a particularly egregious example Delegation. This seems so important because everywhere everyone seems to beat it over your head of how Rust prefers composition over inheritance and how amazing that is. But as a newcomer it seems like the language does not make it easy to do composition. Without proper delegation you have to manually write implementations for newtype methods and traits, when a delegation syntax would be extremely helpful to remove the boilerplate especially when you have so many methods. It seems like a tremendous effort has been put into this RFC and seems to be reasonably popular.

But after 3 years stuck in limbo it was closed because the lang team does not have the bandwidth. They apologize for letting it languish, and I appreciate that and acknowledge how busy they are.
They suggest to bring it up again:

We would like to encourage folks to discuss it when the time comes for us to discuss our upcoming roadmap (one of the procedural changes we have in mind is to make it clearer when we'd be open to bigger proposals).

But how is one supposed to know when they are open to bigger proposals? By then it is very likely that the original author has already lost motivation and a lot of momentum is lost when someone else creates a brand new RFC and starts the whole process again.

There are a few more examples I can bring up, but, in general to me it seems like unless you are a lang team member or one of them is willing to champion your RFC, might as well give up hope on it and prepare to be disappointed.

Would be interested in hearing any alternative perspectives. Do you have examples of a successful significant RFC that was not proposed by a lang team member?