Get rid of call/cc, directly support the few things that people actually build with call/cc, and then you can begin to start to think about improving Scheme.
>>31GOTO usually isn't exposed to the high level programmer. We tend to have loop constructs, switch/cond style trees, dynamic dispatch, and all sorts of actually useful abstractions that are directly applicable to what programmers do, that happen to compile down to GOTO.
What we DON'T do is give the programmer GOTO and tell them to figure out how to make it useful.
The only looping mechanism that Scheme allows is "GOTO start of function" via tail recursion, or fiddle around with mutual recursion in tail calls, which becomes a GOTO loop. The fact that you cannot retain any lexical state as with non-tail calls, but must chain through parameters, is part of the reason it's considered a GOTO.