It's use for generating Console ID for twl is irrelevant for the matter though, not sure why you mentioned it
Let me explain in simple terms since you seem to not read the full thing:
What the page for LocalFriendCodeSeed mentions about it?
"This contains the same LocalFriendCodeSeed data that
PSPXI:GetLocalFriendCodeSeed retrieves from memory."
If you know a bit about programming, you know that a function must be called to get private data, in this case, LocalFriendCodeSeed is called by this to get it's data for something.
Probably is this function also called to get your data on the 002 ban.
Then, on the GetLocalFriendCodeSeed data we get:
"This retrieves the LocalFriendCodeSeed/64-bit consoleID from an u64 already in memory(that memory is initialized by bootrom), which is not loaded from NAND. The source data this retrieves, is also used to generate the console-unique part of the TWL
keyslots, and can be used as part of the keyY when
movable.sed doesn't exist."
Which means about the DSi ware, also that it can be used on common stuff if movable.sed is missing, and that's why I had said that would be nice to keep both changed in case you decide to bypass 002. And, it tells that LocalFriendCodeSeed is a 64-bit consoleID from a bootrom data. If you want to get the part that does not concern the matter, it's up to you, but try reading the whole thing next time before pointing fingers, ok?