Two important considerations are needed:  The account should be configured and have cost associated to it.

When a new AWS account is added to the organization, it must first incur costs before CloudHealth is able to derive the account.  It will not show until costs have been applied to the account and appear on the billing file.

Be sure to review the account configuration and address any accounts that show "NOT CONFIGURED" as those will not have complete information pulled into CloudHealth.

Once those two considerations are met, the platform will pull the account status (Linked, Consolidated, Standalone) based on the information that is read from the AWS billing files, not their association to an AWS organization.

A potential option to ensure accounts are added to organizations as expected is to manually add the new AWS linked accounts into CloudHealth, which will bypass deriving account information from the bill.