This is my own opinion as a person. Please dont think the rest of the fellas from AH think this way but I think it's far too early to make predictions/requests for workflow modifications.
Reason 1.
Implementation of PBR. there are at present 2 well known implementations with UE4 and Unity. One uses the roughness/metalness workflow the other uses spec/gloss work flow. The 2 are similar but have some differences ( though there are some python scripts out there for quick conversions. ) Lets take X-planes implementation which is a hybrid PBR which works particularly well but is a different path to UE4/unity ( at least from my experience ). We dont know the format of the implementation in V4.4
Will there be SSAO?
Will there be packed RGB normal maps?
Reason 2.
Version 5. If there is a new GFX engine coming ( eg vulkan based ) then a lot of the work that a dev might do to get pbr working in V4.4 might go for nothing. Which is to say waste of time. Especially if V4.4 comes out but the rumour mill on V5 gets cranking the uptake of V4.4 might not be as spectacular as the uptake from V3.x to V4.x was. Why would anyone pay for V4.4 then find V5 is around the corner. A bit like having windows 98 then paying for Windows ME with Windows XP on the horizon. ( for you young'uns out there google windows me it was the vista of it's day ).
Reason 2.5.
Commercially wise market size might be a lot more smaller to require it. You talk backwards compatibility within p3d but commercially ask what a dev might need to do. Lets take a westland lysander for example. ( we always use the lysander as a hypothetical plane in AH ... not sure why

) a commercial dev - to be honest a freeware dev as well - would need to do the following.
- A source model for FSX
- A source model for P3d up to V4.3
- a source model for V4.4 if the changes required in materials is widely different -
- and eventually a source model for v5 if V5 gfx engine strays from V4.4 implementation.
Oh and the elephant in the room for commercial devs ? how much all of this backwards compatibility is going to cost in time and money and whether it should be passed onto the customer.
Sorry for the longish post but it is something I've been thinking about a lot.
TL;DR : too early to speculate when we dont know how LM is going to implement PBR.