We include this functionality in cargo-espflash, since we build the project and are able to parse the messages from cargo to determine the artifact path and, if present, use the (possibly configured) bootloader and partition table from these builds.
Since we are not building binaries in espflash I'm not sure we can use the same approach, but it would be nice if we could come up with some solution to this.