would be abolutely not.
UAT of development, depends on how much the environment has an impact, and how close your dev setup is the the production one.
Them developer types have a nasty habit of say putting a software update on so they can use a new feature, without mentioning that it's now a pre-requisite of the fix.
I've seen issues that only appeared on a production server, because Admin forgot to mention something they did on it.
Testing in the development environment, finds errors in the software, in live (or better yet a UAT machine with exactly the same set up as Live) environmental impacts.
If your upgrade and backout plan is reliable and it's not too different fom dev, I suppose you could give it a go, but I've seen some 'trivial' difefrences cause major pratfalls on occasion.
I'd want a box that I could set up to be as close to the production server as practical.
Last time I set this up I was on paired servers one live and one backup, so I used to UAT a new version on the backup, If all went well swap it in. Give it a bit to make I sure hadn't missed anything, then upgrade the other.
That was 24/7 manufacturing, I justified the back up machine, with a half hour stoppage, never mind hardware failures and other potential reasons to have a standby machine.