What do you lose if you use Git for source control management with the RTC-Git interface instead of using RTC v6.0.0 or v6.0.2 for source code management in full?

We have some project teams that want to use Git with the RTC-Git interface for source code management instead of using RTC v6.0.0 or v6.0.2 for source code management in full.
Some specific questions about this include:
1. This is the most important question: Can all traceability links be added between source code and requirements, work items, test cases, etc. when using Git with the RTC-Git interface for source code management?  (These project teams need traceability from Requirements all the way down the V-model to Code and all the way back up the other side of the V-model for testing at every level for SIL functional safety certification.)
2. Can Git change sets be associated with RTC work items when using the RTC-Git interface for source code management?
3. Can source code be shared between teams using Git with the RTC-Git interface and teams using RTC for source code management in full?
4. Is anything else lost when using the RTC-Git interface for source code management?

I have seen the "GIT or RTC source control", "Who has used Git Enterprise and RTC together to manage process for Git source control operations and to associate work items with Git commits", "Jazz Source Control git Emulation" and "Git for source control, RTC for planning & Work Items" posts previously submitted on Jazz.net but none of them answer these questions for these versions (some are very old posts and answers and some of my questions are not addressed in any of them at all).