Yes, it's confusing.

I don't have pictures, sorry. I can describe what happened, an example may make it more clear. I use KAM's battle mod, it contains a projectiles_tables folder with a file named kam_data_core. Because I don't like parts of the changes, I changed it myself and put the file in my own mod (which also contains several other changed tables) under the projectiles_tables folder, I named the file woz_data_core. So you have simply two mod packs each with a projectiles_tables folder and the data file in it. My mod pack is first in order and so should load first completely and overrule all later packs. I thought the game would read all tables of my mod because it is loaded first, and don't read any tables in a later mod for which a table is in my mod. It did so in TW:Attila etc. as far as I see.
Then I saw that my changes were not in the game. I thought it were a display bug, that the unit card did not show the correct setting. But that was wrong. The game read the projectiles_table in KAM's mod although it was second in load order. The other changes of my mod in other tables were in the game. My only explanation is that the game reads the files in the tables of all additional (!) packs if they contain the same tables. The load order is than the alphabetical order of the file names in the tables. Because the file in KAM's projectiles_tables was named kam_data_core and the file in my projectiles_tables was named woz_data_core the game read KAM's file although it was in a mod later in load order.