What ended up solving my problem was to use LimitToPages and avoid paths like '/'.

It seems that if multiple such paths are present, even though only one page actually calls the plugin, it still initiates as if the route applies to ALL PAGES.

So it ends up conflicting and not working (probably throws an error somewhere as well, have yet to find where though). Conflicting, as in, multiple paths that are the same, which '/' is predistined for.

It seems that sometimes the problem is still there even with LimitToPages enabled. This may be inaccurate, but it feels like in some cases only using both LimitToPages and changing the path made a difference.

Heinz Schilling 's answer is still valid to remove the chash, and even caused my links, that were broken ([...]?tx[...]), to at least appear right([..]/detail/[..]), even if they turned out non functional because of the above issues.

Thank you to all that helped!