The only dangerous part of git reset is git reset --hard, which will blow away uncommitted changes. It has a special flag for a reason... it's dangerous.
Beyond that, git reset won't get you anywhere that you can't get back to after consulting the reflog
You can recover from a git reset --hard with the reflog as well, though of course if you had untracked changes you'll lose those. (I usually use git reset --hard in the process of renaming branches and not to get rid of untracked changes, so this isn't a problem for my workflow.)
Beyond that, git reset won't get you anywhere that you can't get back to after consulting the reflog