This is because, by the time a long-latency load event has been seen, it is already too late to try and prefetch its result.
prior works have focused on executing forward slices after a miss event [4, 8, 15, 18, 26], as it is relatively easy to propagate poison bits to squash future instructions or store them for later processing.