Hey Kyle, good questions! It’s hard to say what “Uniswap” as a DAO is “considering”, but the short answer is that the UGP folks who pushed for this grant are definitely interested in seeing this upgrade, and we’re doing our part to try to mobilize the community around an upgrade. So, yes! They’re considering it as much as a whole DAO can consider anything 
This down-in-the-weeds code stuff can be a bit hard to explain, and I’m oversimplifying a bit with this explanation, but the quick TL;DR is that OZ’s Governor works like Bravo’s out of the box, and our extension is written in a backwards compatible way— meaning it adds features without breaking the existing ones.
Here’s a slightly longer explanation:
The OpenZeppelin Governor is basically a modular rewrite of Governor Bravo. Out of the box, it is compatible with Bravo, and is used by many DAO’s these days, such as ENS, as one prominent example.
Because it’s written in a modular manner, it allows for the developers deploying the DAO contracts to customize it by extending or writing extensions. This means if you want, you can definitely modify the OZ Governor to break that Bravo Compatibility to differing degrees, depending on how you choose to customize it.
Our extension is written to be backwards compatible with Bravo-style Governors. This means contract integrations or DAO tools made to work with Bravo should work out of the box with it, but it also enables the new fractional style voting that gives flexible voting all of its flexibility.
Let me know if this explanation isn’t clear or if you have further questions!