No. It is not possible, everything is built and tested against the unstable repository which syncs to shannon (stable) weekly. ISO are built from packages in the repository at the time the ISO is created. There is no way to update a package and build it against the versions of its dependencies on an outdated ISO.
The other distro would not have updated only the driver unless nothing much else had changed since their last release. Might be easier if they are not a rolling release as they block any updates that cause ABI changes anyway so basically nothing important changed. But no distro would go to the effort of putting out a new release and restricting the ISO updating to JUST the driver they would update the whole thing.
A simple mesa update might require a newer version of llvm than was used when the ISO was created which means now you are updating that too and doing the associated patches and rebuilds for that. Then there are many other pieces of the puzzle that might create issues as they are incompatible with said change so you need to update them too which might cause more breakages, so now you work on those...
Now lets assume you finally finish this, you now have a package history of builds that were never in the repository to begin with because you created this patchwork of nonsense completely separate from it.
So no that is not how any of this works, there are no shortcuts possible and this suggestion even if I created the tooling for it to make it possible, it would still be a bad idea and it would be more work than updating the ISO entirely, which as I have pointed out several times before is not the difficult or even time consuming part of putting out a new release.