If you're using that as an argument for why cheating should be allowed, you're missing the key part of what what education is supposed to be about: understanding the fundamentals well enough that you can think of of the box and find solutions without relying on someone to always be there.
Would you really want to work with a software developer who doesn't understand how functions, loops, etc work?
I have, it was pretty awful. At one stage I did a 3-4 week mad panic crunch to fix a system where he managed to hide the problems until it was almost too late. He was the "reverse talent" sort of person, prone to coming up with insane solutions that took more effort to unwind than it would have taken to write it in the first place. But only 20% of the time, so we'd often be left with 80% usable-but-bad code, and 20% WTF code. The crunch was me re-writing everything except the user interface.
Apart from that one incident when I copped it, mostly I felt bad for my team leader who had to babysit the guy all day every day. After the incident above it was changed from "supervise experienced guy" to "babysit".
That company really struggled because they were using a niche language to solve a very niche problem. It was the right language for the problem, but it was very hard to find developers who had used it, let alone who were good at it to the point of being useful in their first year with us. So throwing out Captain Useless took a couple of years.
Would you really want to work with a software developer who doesn't understand how functions, loops, etc work?