I would also like the ability to see a nicely curated set of changes. This mostly exists in the diff tabs of a pull request. If this were to be a first-class feature in git, it seems appropriate to be in some layer other than commits, but alas, that doesn't exist.
I routinely do an interactive one before PRs to clean things up.
If the remote branch is an ancestor of your local branch, you have some commits that haven't been pushed yet and you can "play" with them.
If the remote branch and the local branch point to the same, you can't rebase without potentially impacting someone else.
If the remote branch and the local branch have diverged, it's already too late.
But casually manipulating the order of, or combining or filtering, patches near the top of the tree is something else. There are tools for this, eg
If it's rebased then you're not reading the history; you're reading an artificial modification of what actually happened, performed by someone (possibly past-you) who thinks they know more about what you're trying to do.
I don't rebase precisely because I want to read the history to see what happened.
History flow will show all the meandering around forever, but rebase will remove it and just put the most recent version of the commit on top of the tree. Ie, your log looks like you pushed just the perfect patches each time, every time, and the junk is gone.
With history if you make a vcs mistake, or realize iteratively after pushing that corrections are needed, your worthless threshing around trying to fix it becomes part of your project log forever, instead of just pushing the corrected tree with just the one corrected patch.