I disagree. Most people uses the mempool data wrongly, for eg. reading the chart after successive blocks gives a fee rate that is far lower. You can't predict the future, but it doesn't help if the user don't know what to do with the data. Simply telling them to aim for the top 1vMB of the chart with their fee rates is insufficient.

If you know what you're doing, sure go with the mempool charts. If you don't, then it would often be a better idea to just follow the floating fees given by your client. Fees estimator, or estimation algorithms in general uses the data from the previous blocks, grouping them into buckets for analysis and showing an estimate to the user. It is really not as inaccurate as people think, though admittedly the way it works makes it less responsive than looking at the mempool yourself. At the start, Core's estimation wasn't great but I've seen quite an improvement over the past few versions. It doesn't reflect the state of the mempool in real time, that isn't what floating fees should do.