There is not enough information in your post to answer this. The "seeding process", data submission process, and your consolidation process are specific to your application. Data changes to a single account will cause that entity's calc status for the value member, it's ancestors, and the entity's ancestors, to be impacted for the period in which data changes, through all periods that have data until the end of the current year. There is not a calc status per account but instead per entity-value-year-period-scenario combination. The scope of impacting is also a function of whether you load through FDMEE, or use a form, and whether that form has one or multiple periods. When you calculate data, all impacted data units in the form are calculated. If you force calculate, all data units in the form will be calculated, regardless of their status, so you have to factor this in as well. I wouldn't be quick to imagine a bug is at play (they are rare) but would focus on understanding the application design and process first.
This may be a stretch but did you seed Periodic or YTD? And what are your Scenario settings for Zero View for Non-Adjs? Is the submission for forecast periodic or YTD?