Racket has a good foothold in educational environments, so it's no coincidence that it's conducive to learning. However, Racket also sees a lot of usage in the PL research space, so it's also conducive to just experimenting. Those two combined can make it a very fun environment.
There's also #racket on freenode, which I've found rather welcoming.
On the other hand, if you want to learn Scheme by working through SICP, then I would recommend MIT Scheme to avoid impedance. There's not much benefit from using the Racket ecosystem for that. Likewise, if the goal is to work through On LISP then a common Lisp implementation makes sense.
Of course there's no reason not to have all those languages installed..or at least that's what I tell myself.
My last advice is that Racket is an ecosystem. It provides many languages including Algol and Datalog and Scribble and Typed Racket. This makes for a lot of documentation and it is uneven. The guide will be too shallow and the reference will be more boilerplate rather than providing deeper explanation and further examples.
http://www.neilvandyke.org/racket-sicp/
Also keep in mind there is a different subset language designed by one of the developer/professors for his own book based upon his improvements to the SICP methodology, entitled How to Design Programs, as explained in his paper.
http://www.ccs.neu.edu/racket/pubs/fdpe2002-fffk.pdf
The second edition is available as HTML pages amongst the URLS below.
HtDP is a great book, but no substitute for SICP in terms of content.
I'm in my late 20s going for a second BS (this time in comp sci), and wanted to go through SICP on my own (plus the online lectures). I felt that I needed a bit of a warmup, though, and chose 'Concrete Abstractions' instead of HtDP. I'm satisfied with it so far.
SICP, and this is not a criticism, is more like a stamp collection of computer science topics. It provides a point of reference when I've read about operating systems, state machines, compilers, data structures, etc. etc.
Between the two, SICP is flat out a better book qua book. On the other hand, working through just a little of HtDP will probably have more impact on the way you write software than working through a little of SICP.
Lastly, while there may be some similarities to other introductory texts, I doubt that there is any computing pedagogy backed by as much research as Felleisen and the PLT group. While SICP and Scheme were intended to facilitate teaching, the Racket ecosystem [and PLT Scheme before it] are continuously developed with pedagogy as a primary driver.
Most pedagogy is driven by "I think this would be a better way to teach programming." The PLT group checks their theories statistically and their theories are tied to educational theories in general. And they've been going down that road for several decades.
I do own another Felleisen text (Realm of Racket) that I do intend on reading. And I'm sure, since it's free, I will at least look through HtDP.
However, there hasn't been a release since 2011. The primary maintainer (Chris Hanson) is now at Google, and seems to be busy with other things. Previously, he was at MIT and used to write most of his own research projects in Scheme, so it got a lot more maintenance attention.
Happy Lisping!
If anything, lately Clojure has been drawing on Racket for inspiration in many areas (for example Typed Racket).
In fact, if you wanted to find a criticism of Racket, it might be that occasionally it is "too" modern -- in the sense that some parts are implementations of research papers. You might encounter the occasional module whose documentation isn't much more than "Implements foobars in the sense of Researcher [Year] <link to paywall paper>". To be clear, that is not 98% of Racket. I mention it just to counter the idea that Racket is "less modern". It's constantly evolving with new things.
Finally, for someone getting started with a lisp, Racket is (a) download, (b) install, (c) start coding and running -- within literally 5 minutes. (Of course experienced people aren't limited to DrRacket if they prefer Emacs or Vim or whatever.)