@guru3d - Sounds like you may need to update UBU and or configure it correctly? Maybe you got files mixed up and flashed or checked some other/previous file I sent you possibly??
That, or you did not delete previous BIOS.bin or temp files from UBU when checking maybe?? The info/image I showed was made using BIOS I uploaded, with latest UBU for the image above.
About microcodes, that is normal, look at stock BIOS (There is microcodes in 4x volumes, not 5) - I updated them all, in all volumes, and put all into all volumes (This is correct / how I always do these)
OROM Marvell 88SE9230 - That's supposed to be 1028, see change log

It is possible I uploaded the wrong file!! Sorry, let me check!
* Edit - OK, I checked, and even downloaded the file to be sure too, all correct, this is updated BIOS and all is as shown in the change log above >>

@Kwstas - Sorry, I meant to remove that from the change log (For now, it's on pause while I figure out how to insert that, if it's ever done at all) >>
** Includes >> Secondary BIOS w/ RST replaced with RSTe **
EFI/oRom SATA-RaidDriver v5.5.5.1005 ** Made new/proper FFS if anyone needs **

Anyway, I downloaded the file at #164, everything is correct.
What you are comparing in MC Extractor (BIOS.BIN from mid-UBU run) has the capsule removed, what I showed in change log screenshot for MC Extractor does NOT have capsule removed (See file name)
This is why the offset is not same with what you're checking - capsule is 2KB / 800h = this = difference you are asking about

ASmedia, I only inserted (added) 0.97, did not touch anything else related to ASmedia. Anything you find otherwise is 100% stock from Asus

Post #162 is by Fernando, so not sure what you're referring to there?
Your 2nd to last image above is not the BIOS from post #164 (image says Rampage VI BIOS ). Ohh, I see, yes, that is not this BIOS, that is image of other BIOS Fernando was talking to me about, not this boards BIOS
The last image you showed above is the correct BIOS from #164

Yes, correct, there is NO RSTe in anything here. Sorry for any confusion there, I meant to remove that from change log, but you should have noticed no 2nd BIOS file = no 2nd BIOS file = no RSTe

All cleared up? I think so, BIOS is correct, how it's meant to be, 100% updated, at post #164

@Kwstas - Ask SoniX about that, or insert it yourself with UBU and test. It does not look like it goes with your system, at all
And due to the normal naming scheme, I assume that may be some other series, or incorrectly named version

* Edit @Kwstas - I just tested, it goes in OK But, I'd still ask SoniX why normal rom is named 0.xx and then this random one is 4.xx, AND if 4.xx is compatible with your exact ASMedia onboard controller (read the chip ID for him, or give him devID etc)
Maybe it's just newer, and many versions skipped between 0.xx and 4.27? I do see modified date is 3 years apart.
I'd ask SoniX about all this before we do anything. If it turns out to be compatible, and you want inserted, I can re-wrap BIOS package again for you with that instead of 0.97

I See warning here "ONLY works with Add-On cards"
[Discussion] Firmware for Asmedia Sata 6G Controllers (10)
See also, issues at 184 - [Discussion] Firmware for Asmedia Sata 6G Controllers (13)
And see 4602 (4.27 is for two lane chip only) - [ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions (307)

ALL of this may have been fixed or changed, with the file or how UBU inserts it now, since those are older posts.
This is why it's critical that you ask SoniX directly, if your exact board/controller can use this version, and or if it's better/suggested over 0.97 or 0.95 etc

** Edit 2 - @Kwstas - you can tag SoniX like you did above, or ask directly in the main UBU thread here (where he's more likely to see your question and reply)
[Discussion] UBU Tool related Questions, Reports and Suggestions (105)

About ME, yes, that is due to 8.1.70.1590_1.5MB_PRD_RGN.bin is Stock
and the ME.Bin I sent is Configured for your board and Extracted - You can use either one with ME FW update tool.

@Kwstas - You should ask in the UBU thread, and ask why big jump from 0.97 to 4.27 and if 4.27 is compatible with your X79-Deluxe
I guess you can just test if you want, compare stock BIOS vs 0.97 vs 4.27 in benchmarks etc. I assume there will be ZERO difference in any real comparison, since BIOS does not even have a rom for this anyway

* Edit - @Kwstas - oRom Intel Boot Agent is legacy Boot on LAN Module

*Edit 2 - Check ASMedia chip with your eyes, and flashlight and magnifying glass if necessary.
You should not rely on software, it may not be correct (and in BIOS there is 106x module)

ASMedia SATA, flash that via hardware package, this is not something that goes into or gets loaded out from the BIOS (ie, does not matter what we stick in BIOS, it's not going to be used)
Run that EXE and reboot, then you're done. We need to remove this from the BIOS package, it can be left, but it's just there for no reason

Sorry, I don't know what to tell you about the Windows network thing, I close that window anytime it asks me anyway, I setup stuff how I want
Plus, you do not need to join any domain or workgroup etc. Close that and ignore it.

I put the highest # you can use, without issue = 13.5

@Fernando - Thank you for the above outline for Kwstas! Is that driver only test not affected by the current in BIOS EFI/orom?
I would assume this test would need done with varying BIOS modules as well, once a few narrowed down driver sets are chosen, is this not the case so much as driver?