Not sure I see the calculation breakdown but you do have a lot of subsidiary views that could be the cause. Generally we only use subsidiary views when we need them for filtering (exports and reports). For planning, it's usually better to rely on system modules that carry the mapping. In this way we calculate the value once and refer to it often from one place. This also avoids issues with synchronizing calculations since the calculation is only coming from one place.
@JaredDolich Those subsidiary views are referring to system modules only. Just making Time Scale to None as it was an unnecessary dimension. Do you think of any other reason for those percentages to be correct as per the Level 2 Requirements?