Question related to get_resource_config_history boto3 api call

[Pratyush Mishra]

Does get_resource_config_history() api also contribute to api throttling issues? I was under the impression that config rules use config cmdb(for the resources supported by AWS config CMDB) to look for resource states, but it seems to be a wrong assumption? Or the real question would be, how is it different than making a boto describe api call for the resource? Thank you