Timing analysis - long combinational path

Hi,

Running Timing Analyzer I get violations due to long combinational paths. Looking at the path in the technology map viewer, it looks like this

leftmost block = registerbank holding a configurable value used by the other two modules

center/rightmost block = two identical modules using the register-value

I can see the long path, but I do not understand why it is implemented like this. Why is the register-value routed through dec_filter:15 to dec_filter:9, and not getting the value directly from the register-bank-module to the left?

Is there anything I can do to force a different implementation?