Having static_pool_data with old last_updated_block can cause rate limit?

[NIXBNT]

Bug Description

#391 relevant

• Summary of the bug
  I think the smallest last_updated_block in the static_pool_data is being set as the earliest block to start fetching events from.
  This seems to override the alchemy_max_block_fetch and can cause rate limiting

Severity (High/Medium/Low)

• Rate the severity. High: "I can't/won't use the bot due to this", Low: "I can work around it", Medium: (anything in between).
  Moderate - May cause unexpected limiting

Steps to Reproduce

• Step-by-step reproduction method, include environment information if relevant - such as Python version and OS.
  Put a small blocknumber in the last_updated_block field of the relevant static_pool_data.csv

Expected Behavior

• What should happen
  Blocks should be fetched from current block minus alchemy_max_block_fetch

Actual Behavior

• What currently happens
  Blocks start getting fetched at the oldest block number from the static data

Impact Analysis (to be filled by contributors)

• Automated Tests: Are there existing tests covering this? Do we need new tests?
• Risks: Potential areas affected by this bug and its probable fix
• Performance: Is this bug affecting performance?
• Monitoring: Does this affect any current monitoring? Any new alerts needed?
• Logging: Any changes required in logging?
• Documentation: Updates needed in documentation?