Texture DUPE Deletion script needed

Hi all.. I think I posted this on the wrong forum a bit ago, so I hope this is the correct place this time.

I will tell you what I have and then tell you what I need.

I made a "texture board" with 225 1 x 0.01 x 1 prims (to show textures)
In each one of these prims is the touch text script and are my textures all organized, example follows

Enterior - Walls - Brick
Enterior - Walls - Cement
Enterior - Walls - Growth

Interior - Walls - Borders
Interior - Walls - Wallpaper
Interior - Walls - Curtains

and so forth... now being there is 225 prims on this board you can get an idea of what i have, all catagorized out in thier own catagories. Easier for me this way when in a hurry.
And some of these have the same textures in different ones. I have tried to delete the DUPES the best i can, but that is so time comsuming and even with 3 people clicking on the prim to change textutres.

So what I was thinking is this.

I make ONE prims to hold ALL these textures (not all 225 have something in them) (about 800 or so) and then use a script to delete the DUPES by UUID and then remove itself from the prim/box.
I can then go through all of them again and sort them out by what they are. start all over but would be set.

Also. Maybe have this script instead of deleting itself, stay in the prim for future use, say that you wanted to add another texture names blhablah-oak,.... well there is already an oak in the one that we want to put it in , so when we try to add it to the contents, the script would advise us that that texture is already in the prim with the name if: "XXXXX".

Now the quetions that I have....

1 - is there a limit on a prim to how much it can hold (contents) ?
2 - can there be a script to be made to do these steps. Examine (UUID's), Strip (remove dupe by uuid's) listen (watch out for same texture uuid trying to be added again by uuid) ?
3 - is there a way to add to the script to sort the rest of the textures by catagories? (predefined, allow for up to 225 prims/catagories)

I hope that i am not asking for tooooo much here. but I have seen some of the texture organizers and i have to say,, they are useless to me at this point and time. I am sure they would work for AFTER this fact, but not before. Unless I havent seen one that already does this and doesnt cost an arm and leg. Personally, this is a SL issue and I feel that this should be an SL/LSL GNU/GPL issue. As it effect ALL of us that build/make things FOR SL.

IMHO

Thanks in advance!
KickMe (Please don't (LOL))

Finding key dupes from inventory is simple, a loop in a loop, BUT the procedure will find a lot of false positives.
It will read anything as NULL_KEY that has lacking permissions to read the key and random errors and timeouts will also retuen NULL_KEY.
Automatic deletion (without a backup) is not an option.
Scanning the whole inventory after every inventory change will waste script time.

It is however able to tell you if there are NO key dupes in the inventory.
An advanced version could show you what it thinks to be a dupe and ask for deletion confirmation in that case.

Okay, all that made sence... not. LOL as I dont know the first thing about all this.
Humm.. I think from what you are saying is that this script would look in "Inventory". This is not what I was wanting. I want to add all textures to a prim and then have the script scan that prim loaded with texturs and remove the dupes. Sorry if I am misunderstanding here.

Also, i guess i should have said that I need someone to make one...

Alas, again, I think this is an SL / LL issue, as some people think its best for them to RENAME the textures to something else because it looks like something else and that's where we get 100's of the same textures running around.

I feel that LL / SL needs to add some sort of UUID scanner when someone DOES rename a texture from it's original upload UUID, LL / SL will warn the user, that "The texture you are trying to rename alread exist under the name of "XXXXXX" and your renaming will not be allowed due to ASSET overload.

Now this would not only HELP SL / LL and the ASSEST server issues, but also help and prove productive towards the rest of the community.

KickMe for Pres! LOLOLOL

Thank you for answering and again, sorry that I dont understand all the scripting aspects