This definitely sounds like weird unexpected behavior. I recommend making a support case as I have never heard of this specific behavior before. My hunch is that there is an interaction with the nested calculations that is causing this. It will help support a lot of if you are able to send in a workbook that reproduces the issue so that they can deep dive into how the view experiencing the issue is built.
See instructions for creating a packaged workbook A quick method to anonymize a workbook is to hide any fields containing sensitive information before the data source is extracted. Hidden fields are not included in the final extract.