This is how lossless editing works. This is a BIG concept. Lossless edits never change the original data, edit versions merely store the list of edit operations we specify. If we subsequently edit the data more times later, we never change the original data, we merely edit the list of changes. Then we "output" the change by writing a new JPG file copy, only then the changes are applied, only in the copy. The original data is always kept 100% intact. Other programs, like Adobe, do not know how to apply the list of proprietary changes made by like Sony, same as Sony does not know how to see Adobe changes. Other programs don't understand, so they only see the original data, and necessarily ignore any change list. We write the JPG copy so other programs can see our changes. Lossless editing.
Same way with losslessly editing JPG files, other JPG programs don't understand how to do our methods, and they can only see first JPG original. Lossless edits always have to output new JPG copies so other programs can see it.
The goal is NOT to to be proprietary, but is to be lossless. Any output has to know how to apply the list of changes to a copy of the original data, to output a new JPG copy with changes.
The original remains our stored archived master copy. Subsequent edits do NOT have to suffer undoing previous data shifts, but instead any and every output always begins with the pristine original master and the Current list of edit operations. Edit shifts are done only ONE time, and there is only ONE added set of new JPG artifacts. When we want additional editing in the future, we DISCARD that first expendable JPG output copy, and we edit our list of changes, and then we OUTPUT a new JPG copy for whatever other purposes, which replaces the first expendable JPG copy. Lossless editing.