As long as the breadcrumbs actually HELP your visitors and do not clutter up the page you should be okay.
I agree. I'd add to that that I think it's important that the breadcrumbs serve to lay out the site's structure rather than the path taken to reach a particular page. I've seen breadcrumbs that are dynamically generated based on clicked links, and I don't think that's very useful -- certainly no more useful than a back button, and it means that a little piece of the page's content is changing based on user activity.
I've been seeing breadcrumbs show up in SERPs more often in the past few years, and I think that can be useful from an SEO perspective. Like sitelinks, it provides the searcher with more than one page to choose from, but it also serves to show a piece of the site's taxonomy and give the user the option of going to a page that's higher up in that structure.
For example, if a page about red lederhosen is returned for a search (it's been far too long since I used that example), but the user is more interested in seeing a variety of lederhosen rather than a single product, then seeing something like
Apparel > Traditional > Lederhosen > Red
gives them choices other than clicking through with the assumption they'll have to figure out how to get where they really want to go once they're on the site or running a different search.
Note also that using https://schema.org/breadcrumb may help search engines understand your breadcrumbs, but as long as you're consistent with their use that may not be necessary.