For other operation I am sure that idn reflects changes made on end source on platform side(in idn ui) but for enable/disable and that also on the account status attribute(which is “isActive” in your case) I am not sure. It does reflect account status as enabled/disabled on idn side after successful provisioning which you have confirmed and that is working as expected.
Coming to the actual problem you are worried about:
“This poses a risk because if between an operation and an aggregation we have another operation, IDN will push wrong data via the API call. This can lead to IDN pushing entitlements we removed in a previous operation or disabling an account that we enabled before.”
This would not happen because account status is still reflected properly , it’s just account status attribute is stale.
To overcome the problem you can increase aggregation frequency as much as possible.