I think your interpretation works as long as bookmarking isn't an action.
I can see two workflows here:
As a habitual bookmarker, I'm one of the ones that needed bookmarking to be available anywhere. At its core, I don't care for reacting to be tied to bookmarking, but as long as those are considered the same thing, I love being able to react anywhere on the page as opposed to having to scroll past an article I want to read later just to flag it for later.
This depends on whether you use bookmarking as a way to remember good articles or save them for later reading. It would be interesting to see a convergence of these two where heart/unicorn/dislike stay in between the article and the comments with the bookmark moved off to the side but staying with the viewport as you scroll.
I made a Gitlab Snippet for that subset of "bookmark for later because it's a good resource" articles to keep my reading list purely "to read." It'd be nice if there was a way in site to do both separately, though.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.