Is there a way to more precisely control touched:connect?

Hopefully when I am through, your script will be up and running properly. The first problem you have is the debounce (you call it lock). You are only checking it before the event is triggered and not when the event is triggered. Even if you did, because of the way your structure is, you would have an issue if the player touched multiple different children at the same time. You have the variable defined in a way that once the script changes it, every time anything gets hit, it will wait 1 second and then change the value, which is will not work properly. My way to fix this would be to have a function you call that can localize the variable, thus leading to no mix up errors. For this example I will use the code from the wiki as an example:

local function lock(func)
    local isRunning = false    -- Create a local debounce variable
    return function(...)       -- Return a new function
        if not isRunning then
            isRunning = true

            func(...)          -- Call it with the original arguments

            isRunning = false
        end
    end
end
-- then we attach your event to this:
child.Touched:Connect(lock(test)) -- use uppercase C for connect

Because I have not used the above code before and am unsure about some things I will tell you how I manage it. I have a module script that returns a function and while I am looping through all the items that need touched I put them as arguments to the function my module script returns. The function in the module script contains the Touched event and a debounce. Using that method has always worked for me, but you can decide which path you want to take. Another issue is that you are using a while loop which runs VERY often. I do not recommend that. Read this article for more info. Because you are using the while loop, you may be creating new touched events for the same object. This means that even with a good debounce system your game will continue to have multiple instances of touching. One way to avoid this would be to have an array that contains the objects that you have already created events for (It would require something unique in each object). For instance each child might have a special Id:

local foundIds = {}
local function checkForMatch(list, Id)
    for i,v in pairs(list) do
        if v == Id then
            return false -- if we have already found it no need to continue
        end
    end
    return true -- if nothing has been found we return true
end
for i,v in pairs(whateverParent:GetChildren()) do
    if v:FindFirstChild("Id") then
        if checkForMatch(foundIds, v.Id.Value) then
            table.insert(foundIds, v.Id.Value)
            -- touched event/function here whatever you will do in the future
        end
    end
end -- if they all have unique names then you could just do it by name and not Id   

Another thing to note: while condition do loops should be avoided if there is already an event for what it is trying to accomplish. For instance, instead of looping every few seconds to check and see if the value of a BoolValue changed, I can just use the Changed event for that BoolValue. The same goes for children of objects. There is an event called ChildAdded which fires when a child has been added. So, instead of you looping to catch new children, why don't you use the ChildAdded event. I will note that this may not work in your circumstance. It is just a recommendation from me to you. Finally, the _G. _G usage is not recommended nor encouraged on the Roblox platform because we have things like, IntValues, BoolValues, Other values, The workspace (and other services like ServerStorage), and ModuleScripts. Try to avoid using _G and in your circumstance --I may be wrong-- it seems unnecessary when better, more conventional methods are available. I hope this all helps and have a great day scripting! Note: any additional comments/questions can be asked in the comment section below. gl