Making Hotswap Faster

## Description

Improvements to hotswap which serve the goal of making it faster

## Roles

| Role | User
|---------------------|------------------------------
| Proposed by | @ShadowCat567
| Author(s) | @ShadowCat567
| API Bar Raiser | @rix0rrr
| Stakeholders |

> See [RFC Process](https://github.com/aws/aws-cdk-rfcs#rfc-process) for details

## Workflow

- [x] Tracking issue created (label: `status/proposed`)
- [x] API bar raiser assigned (ping us at [#aws-cdk-rfcs](https://cdk-dev.slack.com/archives/C025ZFGMUCD) if needed)
- [x] Kick off meeting
- [ ] RFC pull request submitted (label: `status/review`)
- [ ] Community reach out (via Slack and/or Twitter)
- [ ] API signed-off (label `status/api-approved` applied to pull request)
- [ ] Final comments period (label: `status/final-comments-period`)
- [ ] Approved and merged (label: `status/approved`)
- [ ] Execution plan submitted (label: `status/planning`)
- [ ] Plan approved and merged (label: `status/implementing`)
- [ ] Implementation complete (label: `status/done`)

---

> Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.

Start by reviewing the issue description and the linked RFC Process to understand the required proposal workflow for faster hotswap improvements. The scope is not defined in this tracking issue; done means progressing the RFC checklist through a submitted and reviewed RFC, rather than completing an implementation.

Written by the indexing model from the issue text.