Timing clocks propagate globally and cannot be restricted to a hierarchical module. It is not recommended to define a scoped timing constraint such as clock group, false path, and max delay datapath only between clocks because the constraint impacts the sign-off timing at a global level for the entire design. To avoid confusion and unexpected coverage beyond the scope of the hierarchical module, such constraints should be defined at the top level.