@heimindanger, I did some digging on the API call you were using and the fields in question. As you reported, the fields exist, but aren't being updated correctly. I can confirm that this is a bug. We did not intend to remove that functionality from our API call and will have it restored in the next minor release.

With regard to the "new" fields. Those were only ever intended to be temporary. The last release removed bandwidth from consensus (keeping it around as soft logic). However, because it needed to be backwards compatible, we had duplicate fields which are now being cleaned up. We have been trying to expose the internal database state as much as possible in our APIs, but in this case it caused some confusion. We have a good layer to create abstractions between internal state and returned state when needed and will make better use of it in the future.