The issue
To me the main identity of the Entangled mod is the Entangled Block's ability to make faces of another block accessible that could otherwise not be reached, as there are few, if any, alternatives for this. Its capability however to be used across unlimited distances, and even across dimensions, make it a very powerful choice for transporting various resources as well.

When trying to balance the different power levels of mods within a modpack, this makes me question if I should rather make the recipe for the Entangled Block more expensive, to account for its incredible usefulness, or to utilise the configuration options to limit its capabilities regarding long-range transport.

The solution
It would be nice if I would not have to choose between one or the other but could simply have an Entangled Block for both - a less expensive one that only works locally and a more expensive one that works with unlimited range, across dimensions. And possibly an intermediary variant which works only within the same dimension, but on a longer, or even unlimited, range.

From what I understand, apart from different textures and recipes for the different blocks, this would not be very hard to implement, you'd, for example, just have to store the values for "allowDimensional" and "maxDistance" in the instance of the EntangledBlock class and make the "canBindTo" method refer to these values instead of to the configuration directly.
But then again I do not truly understand your code, nor do I know what you might have in mind for your mod. From my point of view however this change would be very useful, particularly for modpack makers or others with an eye on the power level of modded content.

Also I request renaming the "Entangled Block" into simply the "Entangler" (just joking), because I kept calling it that anyway and had to edit both the title and the text just seconds are publishing it. Oh my.