That sounds much more specific and accurate. The bug information they gave me basically just referenced having to check the entity's impact status from the database instead of the cache and blamed performance delays on that. I couldn't figure out how that would lead to a longer consolidation specifically when there was an Impact Status rule(though that did probably slow overall consolidations down somewhat).
Thanks again for the information.
Yeah, that sounds a lot like the response I got... which now makes it seem like Oracle doesn't care that they killed performance, you just get to choose how long you put it off.