Ok, this may sound like a dumb simple question , but....

As far as Skyrim goes, a load order will always have conflicts, correct?

In Skyrim, a conflict is when a mod wants to change something that another .esp or .esm has, correct? So not always a bad thing. For example, if you use SMIM mod, in MO you see it has a lot of conflicts with the unofficial patches, dynamic snow, and Realistic Water Two, simply because mesh files are being replaced by it, and/or sometimes the same mesh by them too. So the conflict isn't anything to worry about, mostly just a matter of last one loaded is going to be the last one displayed in game. Correct?

As far as conflicts go, I ONLY need to worry about a conflict if it is anything except a graphic or sound file being changed to look or sound different ?

Reason this seems dumb, I used to mess in programming a little bit many years ago, and back then conflicts pretty much meant the same thing as a bug, which needed fixed, but in Skyrim, I don't think the term 'conflict' is meant in that way, correct?

For example, when I first set up MO a couple days ago, I saw that there was a conflict with wyrmstooth .ini file, because it made a change. Wasn't necessarily a bad thing, just that the mod changed a setting in the .ini file, so other worldspace mods could create grass, cause that setting was naturally turned off in the default .ini file. So in MO, it shows as a conflict because it is changing a value that's already set previously, but not necessarily a problem unless that setting will cause problems with other areas of the game, right?

Correct.

A conflict is just an instance of one file overwriting another. Just look at the conflict and see if it is making a change you want.