I do not know if, or eventually how, AP plans to implement some way to register or record development settings for raw files. There are several requests on the forum to also have Serif produce a DAM, so maybe the emphasis in their bigger picture is to work out a DAM that would be the repository for such recording of development settings and forego the individual sidecar approach - I simply have no idea.
There are two issues - one is the fact that AP has NO method for writing develop settings - I can see where this might be a pain if you do a lot of raw processing and are used to working in raw converters where there is an "all-in-one" environment where you can batch images, etc. Also, virtual copies, etc. Totally, I get that. I personally do not use AP's raw converter.
The second issue is the transferability of raw develop settings amongst raw converters - no one has really even attempted to address this issue probably because it is inherently a dead end. Because each converter does so many things in its own way, there is probably no transfer function that would be useful in terms of translating develop settings from X's application into Y's application. So, the fact the AP does not have this is in line with all other raw converters.
AP is a pixel (and vector!) editor that has a lot of things going for it that PS could stand to learn from. Raw conversion in-app is not really its strong suit.
On the more esoteric side of things, AP supports on the fly FFT noise filtering, OCIO support, inferred LUTs, equirectangular and perspective projection and all sorts of things that PS does not, but that are super useful in pixel editing. These kinds of features are ones that people would probably love to see in PS, but Adobe does not care to implement. If you have features you would like an image editor to implement, roll on over to AP's forum and request them!
If I were to suggest a focus for AP's development team, it would be in the area of macro (actions) robustness and the development of an extensibility API for scripting and plug-in development. Currently AP supports many PS plug-ins natively, but provides no API for making your own - hopefully that will change over time.