This has been explained many times before.
We build OpenEmbedded the way it was meant to, using a full "build image". We also use shared feeds for ARCH packages, these feeds are shared by all boxes with the same ARCH.
The problem is that if package X for box A is build, it creates X.r1 (release 1), and when the same X is build for box B, it creates X.r2, which overwrites r1. If you then flash A, the box will see that r1 is installed in the image, but r2 is in the feed, which it sees as newer, although they are binary identical. This explains why you see updates directly after a flash
The root cause of this problem is in the build toolkit of OpenEmbedded, called Bitbake. It was never designed for building multiple images. It is on my todo list to look into it and try to address this issue.
OE-A images have a completely different way of building images, and doesn't use a shared feed.
All this is not really relevant, as I wrote before, this should not affect the stability of the box in any way, the update from r1 to r2 in this example replaces files with exactly the same (binary equal) files. The only thing you have to do if you see so many files, is do another update once the first is finished, to make sure they are all correctly installed. This is needed due to shortcomings in the design of the package manager (opkg).
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.