Unfortunately, not really (at this moment). The actual tough spot is when the parser is invoked for source validation, completion proposals, text hovering. For example, for completion proposals where we do want the inclusive dot, we have this stack frame between the completion proposal logic, and the actual parser invocation:
`
ScalaTemplateCompiler$.parseAndGenerateCode(Array[String], Array[Byte], String, String, String, String) line: 205	
ScalaTemplateCompiler$.compileVirtual(String, File, File, String, String, String) line: 199	
CompilerUsing$$anonfun$compileTemplateToScalaVirtual$3.apply() line: 40	
CompilerUsing$$anonfun$compileTemplateToScalaVirtual$3.apply() line: 40	
Try$.apply(Function0) line: 161	
CompilerUsing$.compileTemplateToScalaVirtual(String, File, PlayProject) line: 39	
TemplateCompilationUnit.generatedSource() line: 164	
TemplateCompilationUnit.this(IFile) line: 152	
TemplateCompilationUnit$.mkCompilationUnit(IFile) line: 178	
TemplateCompilationUnit$.mkCompilationUnit(IFile) line: 177	
CompilationUnitProvider.fromEditor(ITextEditor) line: 20	
SourceCodeEditor$class.getInteractiveCompilationUnit(TextEditor) line: 47	
TemplateStructuredEditor.getInteractiveCompilationUnit() line: 12	
TemplateStructuredEditor.getInteractiveCompilationUnit() line: 12	
EditorUtils$.getEditorCompilationUnit(ITextEditor) line: 26	
CompletionProposalComputer$$anonfun$1$$anonfun$apply$1.apply(ISourceViewerEditor) line: 62	
CompletionProposalComputer$$anonfun$1$$anonfun$apply$1.apply(Object) line: 62	
Option.flatMap(Function1) line: 170	
CompletionProposalComputer$$anonfun$1.apply() line: 62	
CompletionProposalComputer$$anonfun$1.apply() line: 62	
ScalaTemplateParser$.performTaskWithInclusiveDot(Function0) line: 21	
CompletionProposalComputer.computeCompletionProposals(ITextViewer, Int) line: 61	
`

As you can see, we would need to thread information through getEditorCompilationUnit -> getInteractiveCompilationUnit -> fromEditor -> mkCompilationUnit -> generatedSource -> compileTemplateToScalaVirtual -> compileVirtual -> parseAndGenerateCode. 

Now, I think disconnect problem is really a symptom of a different problem: the fact that (a) we're not reusing compilation units, and (b) we don't control exactly when compilation units perform their compilation (they seem to be doing it greedily upon creation, and then caching results). I think if we fix those issues, we fix this issue.